Upgrade (almost) all outdated project dependencies #2532
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Upgrading (almost) all project dependencies to latest versions. Lots of changes, though largely limited to package.json and test.js files. Possibly something we should pencil in to do occasionally to avoid big shifts like this.
Moved toward specifying explicit semver ranges in package.json for each package, rather than using "*" and deferring to the monorepo or some other package. Better to be explicit and use tools to keep things in sync. Monorepolint can get us some of the way, though once we move to a modern yarn that will allow an even cleaner approach to keeping things consistent.
Some code changes required though only to utility and test scripts, and then only function name changes e.g. load.sync() is now loadJsonFileSync() in the latest version. Shouldn't be any changes to module behaviour.
Removing chroma-js as a turf-isobands devDependency as it doesn't seem to be used.
Please fill in this template.
npm test
at the sub modules where changes have occurred.npm run lint
to ensure code style at the turf module level.Submitting a new TurfJS Module.
n/a