-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
NW Executable File Size: make a lightweight standalone executable #3955
Comments
@loretoparisi, as far as I know, the newest development of NW JS (the v0.13 alphas) is geared at solving that problem by providing 3 different build types: SDK (one with debugger / Chromium developer tools), normal, and then one with native client support. As far as I know, the SDK version is most like what is available in 0.12.3, which adds a bit of bloat. My experience is that the resulting NW JS builds compress down fairly well though; where I'm seeing something like 80 MB down to about 30 MB. |
@puzzud Ok, so I'm going to try the 0.13 alpha5. I confirm that compressing the app it is downsized to about 30MB, but how do you managed that, I mean it's ok to distribute, and you did like a native installer that unzip everything? |
Using nwbuilder I get a stable 49.1% compression, 77mb -> 38mb. I would also like to see a more distributel friendly version. |
I tried with UPX which compresses nw13-alpha3 sdk for win32 from 66M to 23M. But a known issue is that UPX will strip off all the debug info from executables. |
@makkesk8 thank you, I think I will try this way, since I need first a binary that is a stripped down version of the current one. Then as soon as I get a smaller executable, the compressed package will be distributed with a mac installer (if on mac). I will post here my results. |
@loretoparisi That result wasn't 100% accurate since I have a gulp script that builds it with nw-builder then to NSIS so total package with installer is 38 mb, Me saying this doesn't really matter since the installer is just +/- a mb or two. But you should see a similar result :) |
The executable file size for
are
This means, that making a simple app package without any other external resource, generates a package that is about 70MB up to 100MB for MacOS .app like:
where I just have
Is there any way to compile Chromium in order to strip down unnecessary libraries, etc to shrink it, let's say a light build like 20-30MB for the NW standalone?
Thank you.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: