Webpack 5 compatibility issues #70
Open
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
|
Since this project seems unmaintained, I published a new working fork of that, if you need it use |
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.
Since webpack has changed some plugin hooks, this plugin is no longer compatible with the newer versions. the culprit is the line
compiler.plugin('emit', (compilation, callback) => {who conflicts with the new hooks and throw an error during bundiling.
To implement the plugin now is needed
compiler.hooks.emit.tapAsyncWhile I was there I got carried away and I've standardized the development environment and updated the packages to the latest versions, some of these like React required some code adaptations (the core is untouched)