[RFC] Standardize to Node 16 and NPM 8 #559
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.
Summary
This PR standardizes our setup to use Node 16 and NPM 8, which enters active LTS recently. It's the first Node version that comes with NPM 8 (which doesn't change a lot for our purposes compared to NPM 7).
Reasons for this change:
npm -i -g npm
. It causes us to constantly remind them to revertpackage-lock.json
changes.Notes
Everyone should download Node 16 from website once it's merged.
Test Plan
CI. Shouldn't have any user visible changes.