This repository has been archived by the owner on Nov 21, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 34
Don't package node with the final app #16
Comments
This is a duplicate of #9 |
@iCrazyBlaze Your suggestion should at most be an option not applied by default. I prefer large file sizes than network traffic for example. |
@iCrazyBlaze: Thanks for the suggestion. I can think of three possible interpretations for what you said:
In summary, I really appreciate the idea but I’m closing this for now. If there’s something I’m missing, please reopen and we’ll talk about it. |
Some updates: In version 2.0.0 there are advanced command-line options that allow you to customize the build, and you may achieve what you want using these options as part of a more sophisticated build process. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Caxa should instead download the correct NodeJS version if it is not already installed on the system. Otherwise, it should run the version that is already installed.
The binaries for v14.16.1 (win x64) are located here: https://nodejs.org/dist/v14.16.1/win-x64/
This will help with the ridiculous file sizes.
The text was updated successfully, but these errors were encountered: