Chore: Upgrade webpack 4 to 5#2604
Open
WinstonPoh wants to merge 4 commits into
Open
Conversation
- ts problems - nodemon/gulp issues - tsconfig transpilation issues
- Move FullChannel type alias below import block (import/first) - Merge duplicate app/constants import (import/no-duplicates) - Suppress no-unused-vars on base-class no-op stopHeartbeat param Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
1 participant
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.
It would be nice to use newer version of Node. However, webpack 4 is not compatible by default with Node.js versions 17+ which use OpenSSL 3.0.
This incompatibility stems from OpenSSL 3.0 disabling the older, insecure MD4 hash algorithm that webpack 4 uses internally for content hashing.
webpack 5 is OK