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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bundling error with 3.1.1 #25
Comments
@hugogiraudel I don't understand. Why doesn't webpack pick up the module field from pkg.json pointing to the ES6 source? Line 6 in 4ace17d
So, what should we do / export then? Go back to UMD or is there a way to make it work like this by exporting an IIFE? 馃
Thanks, makes sense. |
As of right now, version 3.1.1 is breaking a lot of builds because of the change of export. Since it is not possible to unpublish a version, I suggest you either:
Maybe we ask someone from Webpack to shed some light on that issue once the fix has been published. :) |
I am looking at this webpack/webpack#1979, maybe it is related. |
@hugogiraudel Could you share the part of your webpack config where you specify the |
Anyway, here is 3.1.2 unbreaking the issue. 3.1.1 will be remembered as the rogue one. Thanks! :) |
Good morning! 馃憢
As per 3.1.1 (which changed bundling system to
iife
), Webpack bundling ofclasscat
causes the following error:With all due respect, I suggest not changing what your library exports in a patch. 馃槃
You probably should roll back to 3.1.0 or publish 3.1.2 with
amd
bundling and offeriife
in 4.0.0 or optionally in a minor along side with the existing export interface.Hope it helps!
The text was updated successfully, but these errors were encountered: