-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
generateAsync doesn't work and there was no error #724
Comments
same issue here on 3.5.0 |
I also had generateAsync die silently on me. We're using Webpack 5.9.0 and had to downgrade JSZip to 3.2.0 to get it working. |
|
这个库是对图片大小有限制吗 |
Yup using 3.2.0 fixed the issue for me |
Had the same issue. async won't resolve using the 3.5.0 version from npm. Fixed with 3.2.0. |
I've been looking into this. 3.5.0 does work, but you have to change your imports to use I have a feeling it's because of 617e3ce causing Webpack 5 to get something wrong in module resolution. Update: Found a fix, I'll send a PR. |
I've been looking into exactly why Webpack is hanging silently. One thing I noticed is that in Webpack 5, since it doesn't include polyfills and globals by default, people have to use the Line 7 in 25d401e
This was likely already an issue before Webpack 5. The There's likely a switch somewhere that switches to a NodeJS stream that never emits events in a browser, causing a silent failure from this hanging promise. jszip/lib/stream/StreamHelper.js Lines 77 to 105 in 25d401e
Anyways, that's why it hangs without an error. Browsers should use the |
Unfortunately my time is very limited at the moment so haven't been able to confirm this fix. However, I've published #742 as version |
@Stuk can confirm it works now, was hanging before for me as well. Thanks! |
@MichaelFedora thanks for checking! Fix published in 3.6.0 |
generateAsync对20个图片进行打包压缩时,该方法没有执行,且没有报错
The text was updated successfully, but these errors were encountered: