-
Notifications
You must be signed in to change notification settings - Fork 9
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
Support Webpack v5 #6
Comments
Webpack v5 seems to be compatible despite I recall that recent versions of Webpack (since v4 I think?) have better support for complex objects via |
A warning? I see NPM ERROR, @arthanzel : Used stack: npm -v |
Ah, it seems I'm still using npm v6. v7 changes peer dependency resolution and errors if an incorrect version is found. Thanks for bringing this up. I'll re-open this and investigate the DefinePlugin approach in newer Webpacks. If |
@ivaylopetrovdev Could you let me know if the DefinePlugin approach works for you, or if you find any weird edge cases where it fails? |
@arthanzel Unfortunately I'm not familiar with the 'DefinePlugin approach' and how it should works. I will do some additional tests first so I can prepare up-to-date version of my application with Webpack4, before I switch again to Webpack5. Will let you know if I find something weird. |
The Webpack docs describe it well. It takes about the same amount of effort to set up. |
@arthanzel in this case, can we have a peerDependencies update or detailed description how it should be done for the Webpack v5 case please? |
I was searching around and found this too, this seems to be the simplest solution that works with Webpack 5. I also created a codesandbox here (link) to show it working.
|
We need config-webpack to be compatible and tested with Webpack version 5.x.
When this will be possible? If not soon, when we can expect this support?
The text was updated successfully, but these errors were encountered: