Bump node.js version to 22 #1797
Merged
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
rmunn
added
the
engineering
Unit Test Results362 tests 362 ✅ 12s ⏱️ Results for commit 8979982. |
This was referenced Apr 30, 2024
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.
Fixes #1794
Description
Node 22 just came out, so we want to upgrade off of Node 16 which is going end-of-life today (end of April 2024). This PR moves
straight to Node 22.
This requires upgrading webpack, as webpack 5.27.1 used a feature of older Node versions that is deprecated in Node 18 and above. No other NPM package upgrades have been required yet; once we're running a modern version of Node, I'll upgrade more NPM packages.
Screenshots
N/A
Checklist
Testing
make, make sure site still loads. That's about it.