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
Zipping best practice #581
Comments
Thanks! I haven't even reached here but this is definitely good to know before getting into zip functionality. |
If you put all your files in a Because the user downloads the zip file, then extracts everything once to a folder, then deletes the original zip. This has no impact on performance. |
There are so many options for zip functionality that it sometimes gets confusing. To make sure I understand we have a |
You got it, you can download the example I linked above. but that's it:
|
Closing this in favour of #623. |
Current Docs/API:
This approach has come to be known as an anti-pattern, it should no longer be enabled by default or recommended in the new API.
This approach involves packaging your project code into a
.zip
then performingcopy /b nw.exe+package.zip app.exe
orcat nw package.zip > app && chmod +x app
. Producing an executable with the zip file built-in to it.When you double-click the executable, the first thing it does is extract the zip file contents to a temp folder, then launch the app from that location. This requires unzipping the project files on every launch, making the start up time for apps slow for no benefit.
A better approach is to store the project files in a
package.nw
folder and place the folder next to thenw.exe
. So it just runs directly from the file system.The text was updated successfully, but these errors were encountered: