chore: upgrade to Node 18 #8846
Closed
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
Review or Edit in CodeSandboxOpen the branch in Web Editor • VS Code • Insiders |
Upgrade webpack from v4 to v5 to support Node 18's OpenSSL 3.0 natively, eliminating the need for the deprecated --openssl-legacy-provider flag. - Upgrade webpack: ~4.31.0 → ^5.88.0 - Upgrade webpack-cli: ~3.3.2 → ^5.1.0 - Upgrade webpack-dev-server: ~3.3.1 → ^4.15.0 - Upgrade source-map-loader: ~0.2.3 → ^4.0.0 - Update libraryTarget to library.type format (webpack 5 breaking change) - Replace -p flag with --mode production in build scripts - Update engines.node to >= 18.0.0
Contributor
Author
|
Need to upgrade webpack first. |
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.
Upgrades the codebase from Node 16 to Node 18.
Changes
Why Node 18?
Node 18 is the current LTS version and provides better performance, security updates, and modern JavaScript features. This upgrade ensures we're using a supported Node version.
Webpack 5 Upgrade
Upgraded webpack in codesandbox-browserfs from v4 to v5 to eliminate the need for the deprecated
--openssl-legacy-providerflag. Webpack 4 uses legacy OpenSSL algorithms that are incompatible with Node 18's OpenSSL 3.0. The upgrade includes:-pflag with--mode productionin build scriptsAdditional Fix
Added resolution to use local workspace version of @codesandbox/components in sse-loading-screen to prevent it from pulling the old npm version that still requires Node 16.