Upgrade to Node 18 #19
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
rajadain
approved these changes
Aug 8, 2022
|
Reminder to add a CHANGELOG entry before merging! |
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.
Overview
Node 16 will soon be out-of-date as Node 18 is set to become the LTS version in October 2022.
Connects #17
Notes
The only issue with upgrading has been a cryptic error that seems to be related to openssl:
Forcing node to use a legacy ssl provider is a temporary workaround. More info can be found in the node release notes.
I think the root cause is a module that's using unsupported openssl functions. If there is a way to get webpack to output more logging info while it's bundling, it could help track down which module it might be coming from.