Open jurassix opened 3 years ago
I've investigated this, and the API for WP5 has changed a bit, and a lot of the changes this plugin makes would be considered 'hacks' around the API. I spent a little bit hacking them back into place but honestly it would likely be better for someone to do it from scratch rather than modify this plugin.
As you noticed, in many ways this plugin has had to work around limitations in extending webpack. Every major version update of webpack equates to many many hours of testing and dev work.
While I'd like to support webpack 5, right now I just don't have the time to devote to that endeavor.
Is there anything from a webpack side of things you need help with?
Is there any update on this?
Hi, we migrated to webpack 5 and would be neat to have support of this plugin
This alternative did the trick for me: https://www.npmjs.com/package/google-closure-library-webpack-plugin
Using:
npm install --legacy-peer-deps
allows me to use webpack 5. would be nice to have this in the repo, though.
https://www.npmjs.com/package/google-closure-library-webpack-plugin does not have even example of how to use it
Any updates on webpack v5?
👋 I'm interested in using GCC with the latest version of Webpack (v5) but there seems to be an internal plugin issue. So far I've upgraded the demos to the latest dependency versions and included the error below. I've also checked to see if there is a v5 working branch but didn't see one. I'm happy to contribute to help get the latest webpack version supported but unsure if there is already work in-progress. Thanks for your time.
I get the following error after upgrading the
es5-and-es6
demo: