-
Notifications
You must be signed in to change notification settings - Fork 252
rfc: Suggest similar script names for npm run #9
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
Conversation
This was originally discussed here: npm/npm#20741 Equivalent Yarn issue: yarnpkg/yarn#5867
accepted/0000-run-suggestions.md
Outdated
|
|
||
| > This is required, even if it seems like a stretch | ||
|
|
||
| I'm sorry, but I can't come up with alternatives to help with this problem. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Alternatives: List all scripts, keep current behavior.
|
Also, could you please create a corresponding thread for this in https://npm.community/c/ideas/rfcs? |
Whenever npm run 'script' is unable to find 'script', display a list with all possible available scripts. Refs: npm/rfcs#9 Fixes: npm#20858
|
I also support this idea to save more time of debugging for developers. Then I made a patch at npm/npm#20879 and it's shipped already :) We might want to close this issue as resolved. |
zkat
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I mean we merged this, so ;p
I'll take care of wrapping up the RFC tomorrow. Thanks for this! Excited to have it, and thanks to @watilde for taking the initiative with implementing it!
This was originally discussed here: npm/npm#20741
Equivalent Yarn issue: yarnpkg/yarn#5867