You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I'm new to launchui packager, and earlier today I terminated the launchui package download process accidentally, now it can't run and gives the following error output.
Packaging some-project version 0.0.1 for win32-x64
Extracting launchui-v0.1.4-win32-x64.zip
Error: end of central directory record signature not found
at C:\Program Files\nodejs\node_modules\launchui-packager\node_modules\yauzl\index.js:167:14
at C:\Program Files\nodejs\node_modules\launchui-packager\node_modules\yauzl\index.js:473:5
at C:\Program Files\nodejs\node_modules\launchui-packager\node_modules\fd-slicer\index.js:32:7
at FSReqWrap.wrapper [as oncomplete] (fs.js:467:17)
And after a clean reinstall, the problem still persists.
C:\Windows\system32>npm remove --global launchui-packager
removed 169 packages in 0.675s
C:\Windows\system32>npm install --global launchui-packager
C:\Program Files\nodejs\launchui-packager -> C:\Program Files\nodejs\node_modules\launchui-packager\cli.js
+ [email protected]
added 169 packages from 126 contributors in 4.038s
After doing some search, I found out that the downloaded package file is located in: C:\Users\Username\.launchui\launchui-version-arch.zip.
There should be some clean up code after the unzip function returning unexpectedly so it can re-obtain the file in case the file is damaged.
The text was updated successfully, but these errors were encountered:
Hi, I'm new to launchui packager, and earlier today I terminated the launchui package download process accidentally, now it can't run and gives the following error output.
And after a clean reinstall, the problem still persists.
After doing some search, I found out that the downloaded package file is located in:
C:\Users\Username\.launchui\launchui-version-arch.zip
.There should be some clean up code after the unzip function returning unexpectedly so it can re-obtain the file in case the file is damaged.
The text was updated successfully, but these errors were encountered: