Update our CI pipelines to include Node 18 #4278
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
…hout the "--openssl-legacy-provider" workaround
octogonz
requested review from
iclanton,
apostolisms,
D4N14L and
dmichon-msft
as code owners
iclanton
approved these changes
Aug 11, 2023
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.
Summary
Node 18 has been LTS since 2022-10-25, but our CI pipelines have not been building it because of incompatibility with Webpack 4.
Details
heft-webpack4-pluginnow prints a warning if Node 18 is used without theNODE_OPTIONS=--openssl-legacy-providerworkaroundNodeJsCompatibility.tsto specify 18 as the new LTSautoinstaller.locksometimes appears in my Git diff view, so I've added*.lockto .gitignore and synced up therush inittemplateHow it was tested
@TheLarkInn @iclanton