You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to use the command line feature to configure my app like so
$myapp --update --config --file --or --whatever
It could be there is a different script in the package.json that will be run on cli or so.
The main reason is the use case where the user runs the cli without parameters. Here I would like to display program usage as per usual, but there is no way(?) to differ between service starting and starting from cli.
The text was updated successfully, but these errors were encountered:
I'm thinking a "cli" key in the "scripts" key in the package.json file. This way we can make it so that if this key is not present, it defaults to what you have now. This way it will not break backwards compatibility.
Another option is to add a way to disable the cli. That way I can plop a different cli in /usr/local/bin/ with the myapp name using the "extra_files" option.
I would like to use the command line feature to configure my app like so
It could be there is a different script in the package.json that will be run on cli or so.
The main reason is the use case where the user runs the cli without parameters. Here I would like to display program usage as per usual, but there is no way(?) to differ between service starting and starting from cli.
The text was updated successfully, but these errors were encountered: