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
RFC #623
Comments
IMO, all of this would be nice but none of it should be part of |
I agree with @sysrage, separating CLI and docker stuff makes sense to me. It lets their repo(s) be more scoped to the specific problem it is trying to solve. And it keeps the
But in general I like the idea of having some tooling that simplifies the process of using Docker and building each platform in their native environment, with their correct Node versions. That solves a lot of problems. |
I knew what I wanted to build but didn't know if I should add it to a pre-existing tool like |
Working on it here: |
Awesome! Might I suggest a name change, since many/most of the features aren't actually related to a "build" process? 😉 |
Sure! I made this a while ago and wasn't sure of it's purpose. |
Motivation for this was due to https://github.com/electron-userland/electron-builder and https://github.com/electron-userland/electron-forge. Essentially an all in one build tool but for NW.js |
API v4
Install one or more NW.js binaries.
nwbuild
automatically looks for thenw.develop.json
manifest which defines options which are more suited for development.nwbuild
automatically looks for thenw.package.json
manifest which defines options which are more suited for packaging.An installer for the packaged applications.
The text was updated successfully, but these errors were encountered: