Update frontend to Node 16 #186
Merged
Conversation
This file contains 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
alexjball
force-pushed
the
upgrade-node
branch
2 times, most recently
from
ea42fda
to
e9f12ff
Compare
Also use newest version of setup-node, which automatically handles caching.
alexjball
force-pushed
the
upgrade-node
branch
from
e9f12ff
to
e78d570
Compare
JMStudiosJoe
approved these changes
Oct 11, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This updates to use Node 16 and NPM 7, which will shortly become the active LTS release. NPM 6 and 7 use different lockfile formats so this should hopefully ensure consistent usage.