Skip to content
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

alternative syntax #30

Closed
boneskull opened this issue Apr 17, 2016 · 1 comment
Closed

alternative syntax #30

boneskull opened this issue Apr 17, 2016 · 1 comment

Comments

@boneskull
Copy link
Contributor

What if:

{
  "scripts": {
    "scripty": "scripty"
  }
}
$ npm run scripty my:script

???

@searls
Copy link
Member

searls commented Apr 18, 2016

👎, I think it's how I would want it to be honest

First, the purpose of the module is to allow folks to extract scripts as a refactor without changing their existing CLI commands (e.g. Whoever introduces scripty doesn't need to educate their team to start running a new command, they can just keep running, say, npm run foo:bar as always).

Second, if there is any confusion as to where a script is or how it's implemented, all someone needs to do is run it and the first thing scripty does is tell you what it is running. If it's too hard for contributors to figure out, folks could document it however they like ("test": "scripty #see scripts/test")

@searls searls closed this as completed Apr 18, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants