This repository has been archived by the owner on Feb 18, 2024. It is now read-only.
Refresh lockfile & bump in-range dependency versions #848
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.
The refreshed lockfile brings with it webpack 4.7.0 amongst other things, and will make it easier to differentiate between the Babel 7 performance changes and everything else when using linked packages, than if the full lockfile refresh were in the Babel 7 PR.
Bumping the version ranges themselves in theory shouldn't be necessary, however it reduces the chance of end-users package-managers consolidating deps with an older version & making it harder when we try to debug any issues (webpack itself does the same).
To future self: This was generated using a global install of npm-check-updates, but due to bugs it has to be used outside of lerna and also after deleting all
node_modules
in the monorepo. There is also a bug with combining--upgradeAll
and--semverLevel minor
, so packages that had major version bumps (eg deepmerge) had to be excluded manually using-x
, and the--semverLevel
option not used at all. (Why do I seem to be the only one that finds all of these types of bugs...?!)