Conversation
Contributor
Author
|
As we can see from the CI, webpack 5.0.0 no longer works for the minimum Node.js 18.20.0, so we have to bump webpack requirements as well. I will try to find the first version that webpack 5 even supports Node.js 18.20.0. |
JLHwung
changed the title
^18.20.0 || ^20.10.0 || >=22.0.0^18.20.0 || ^20.10.0 || >=22.0.0 and webpack requirement to >= 5.61.0
This was referenced Jul 15, 2024
nicolo-ribaudo
approved these changes
Jul 15, 2024
liuxingbaoyu
approved these changes
Jul 15, 2024
Merged
anon87088-max
approved these changes
Jan 30, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Please Read the CONTRIBUTING Guidelines
In particular the portion on Commit Message Formatting
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
What is the current behavior? (You can also link to an open issue here)
Behaviour is not expected to change.
What is the new behavior?
Does this PR introduce a breaking change?
If this PR contains a breaking change, please describe the following...
Dropped support for dead node.js versions and old webpack 5 versions.
^18.20.0 || ^20.10.0 || >=22.0.0and webpack to>= 5.61.0or pin babel-loader to 9Other information:
The webpack requirement is bumped to 5.61.0 as this is the first webpack version that supports the Node.js 18 change without the
--openssl-legacy-providerswitch: webpack/webpack@0f6c78c