-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make changes for Webpack 5 #46
base: master
Are you sure you want to change the base?
Make changes for Webpack 5 #46
Conversation
It seems like the UTs fail in master on Windows. Would be good to confirm if the tests pass in Mac/Linux before and after this change. |
I'd like to have this released and I can help you with linux test if you'll hold my hand with the process… |
Thanks for the offer! I'm not a maintainer of the project, so I won't be able to merge the PR. But the thing I'd like to confirm here is that the tests pass in master and in this PR branch, as they fail in both places on my windows machine. I just cloned the repo, ran |
Well ... I'm not sure if this is an OK run, but that's what I get from
(yep, just 3 empty lines) |
FWIW we maintain a fork of this project with webpack 5 support. |
Any update about this PR? Is it ready to merge into master branch? |
As part of the effort to update to webpack5 (#9568) this updates a few webpack related packages, hopefully reducing the number of issues when updating webpack itself. The most significant change is migrating from duplicate-package-checker-webpack-plugin to its fork @cerner/duplicate-package-checker-webpack-plugin because the original has not merged support for webpack5, see darrenscerri/duplicate-package-checker-webpack-plugin#46 Co-authored-by: Craig Macomber <[email protected]>
This will address the deprecation warning that comes with Webpack 5. Should resolve #42