-
Notifications
You must be signed in to change notification settings - Fork 300
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
Match all options in API, CLI and package.json
#67
Comments
Here's a bit of an overview of what is/isn't supported. Options:
Options
‡ This should be called something like "namingScheme", or better yet "buildNamingScheme". It's bad form to pass options by scope. Options should be passed with an object as a parameter. It's better form and even potentially faster to type. |
Here we go #73:
💥 |
"Boom!" |
Why not make all options available in package.json? |
+1 for all options in package.json and/or all options available as cli arguments. Situation right now is somewhat confusing. |
I want this feature 😍 |
I'd really appreciate it if someone could make a pull-request to add these please 😄 |
Why use this over electron? |
package.json
package.json
package.json
package.json
package.json
and CLI
package.json
and CLIpackage.json
package.json
package.json
So that we can just write up an npm script for building instead of using Grunt/Gulp or the programmatic API.
The text was updated successfully, but these errors were encountered: