Upgrade npm dev dependencies #836
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Manually install `esm` as part of the legacy test job, and ignore the lockfile
|
Note: merging this pull request separately may cause conflicts with other pull requests I've raised. I'd recommend only merging #837, which combines several upgrades in a single place. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Bump a bunch of dev dependency versions in package.json to more recent ones.
These aren't all the latest versions available, as some of those caused breaking changes in the tests. Therefore, I've stopped at the most recent version I could find without a breaking change.
As part of this, I've had to move the node 10 tests into the "legacy" matrix. (I'm not entirely sure which of the upgrades broke it specifically).