Code Monkey home page Code Monkey logo

Comments (7)

evshiron avatar evshiron commented on July 17, 2024

@rstacruz ahuh, what options are you using? Did you try --production or --side-by-side option? Do you know who is occupying most of the space?

from nwjs-builder.

rstacruz avatar rstacruz commented on July 17, 2024

ahh, i'll have to try those! what's side-by-side?

from nwjs-builder.

evshiron avatar evshiron commented on July 17, 2024

--side-by-side means not to combine the application package to the executable (that copy /b nw+app.nw app step).
From #47, I assume you are running nwjs-builder directly in your project root, which will no doubt include every file in that directory.
You might want to read Development section which I have explained why there isn't an excluding option.
Most of the time you might be using some compilers/transpilers to transform the source code and have a lot of dependencies only used in development stage, along with tests and scripts. They are not going to be packaged when doing a release.
So my suggestion is filling release files to a directory and using nwjs-builder to pack that directory. So there is no excluding needed :)

from nwjs-builder.

rstacruz avatar rstacruz commented on July 17, 2024

Ahhh, right. My app uses no transpilation (node.js 6 supports most of es6
anyway), so I was pretty concerned about that!

On Tue, Jul 26, 2016, 4:02 PM Evshiron Magicka [email protected]
wrote:

--side-by-side means not to combine the application package to the
executable (that copy /b nw+app.nw app step).
From #47 #47, I assume
you are running nwjs-builder directly in your project root, which will no
doubt include every file in that directory.
You might want to read Development
https://github.com/evshiron/nwjs-builder#development section which I
have explained why there isn't an excluding option.
Most of the time you might be using some compilers/transpilers to
transform the source code and have a lot of dependencies only used in
development stage, along with tests and scripts. They are not going to be
packaged when doing a release.
So my suggestion is filling release files to a directory and using
nwjs-builder to pack that directory. So there is no excluding needed :)


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#46 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAEikd6vytCrXzOmnS9mI88nbD3zdg4Gks5qZb8qgaJpZM4JU159
.

from nwjs-builder.

rstacruz avatar rstacruz commented on July 17, 2024

Any hints on how to do that? Will I need 2 package.json's?

On Tue, Jul 26, 2016, 4:12 PM Rico Notifications <
[email protected]> wrote:

Ahhh, right. My app uses no transpilation (node.js 6 supports most of es6
anyway), so I was pretty concerned about that!

On Tue, Jul 26, 2016, 4:02 PM Evshiron Magicka [email protected]
wrote:

--side-by-side means not to combine the application package to the
executable (that copy /b nw+app.nw app step).
From #47 #47, I assume
you are running nwjs-builder directly in your project root, which will
no doubt include every file in that directory.
You might want to read Development
https://github.com/evshiron/nwjs-builder#development section which I
have explained why there isn't an excluding option.
Most of the time you might be using some compilers/transpilers to
transform the source code and have a lot of dependencies only used in
development stage, along with tests and scripts. They are not going to be
packaged when doing a release.
So my suggestion is filling release files to a directory and using
nwjs-builder to pack that directory. So there is no excluding needed :)


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#46 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAEikd6vytCrXzOmnS9mI88nbD3zdg4Gks5qZb8qgaJpZM4JU159
.

from nwjs-builder.

evshiron avatar evshiron commented on July 17, 2024

node.js 6.x is cool :)
nwjs-builder used to require extra flags like --harmony-destructuring to work on node.js 4.x/5.x, and doesn't support legacy versions. But after publishing there were complaints for it and I started to use babel :)

from nwjs-builder.

evshiron avatar evshiron commented on July 17, 2024

@rstacruz No. You can write a build.sh (or any other task runners) which copies every file you want to include (like package.json) to a separate directory and call nwjs-builder to make a bundle of it.

from nwjs-builder.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.