NW.js throws error when zip file not present on every execution
See original GitHub issueNWJS Version : 0.64 Operating System : Windows 10
After closing program file debug.log is created alongside nw.exe with strange contents:
[0514/214309.922:ERROR:zip_reader.cc(132)] Cannot open ZIP from file handle 00000000000001A8
[0514/214309.922:ERROR:zip.cc(202)] Cannot open ZIP from file handle 00000000000001A
Issue Analytics
- State:
- Created a year ago
- Reactions:6
- Comments:15 (3 by maintainers)
Top Results From Across the Web
how to handle error while extracing the zip file in node.js
After looking in the code from adm-zip, the only way is to embed extraction in a try {} catch statement: var zip =...
Read more >NW.js v0.67.1 Released with Node.js v18.7.0
Here is NW v0.67.1 with Node.js v18.7.0. ... Fix: NW.js throws error when zip file not present on every execution (#7882).
Read more >How To Work With Zip Files in Node.js - DigitalOcean
In this step, you'll read and list all files in a ZIP archive using adm-zip . To do that, you'll instantiate the adm-zip...
Read more >Best methods for unzipping files in Node.js - LogRocket Blog
Using zip files in your Node.js project effectively reduce file size while ... extraction without blocking code execution using Promises .
Read more >throw - JavaScript - MDN Web Docs - Mozilla
The throw statement throws a user-defined exception. Execution of the current function will stop (the statements after throw won't be ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Fix released with 0.67.1
This does happen with 0.66.0. It is not a configuration issue, it is a bug that @rogerwang will need to fix.