-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Allow user to specify which script a subcommand should call #532
Comments
2 years... will this issue never be addressed? 😞 it is an extremely useful feature that you can use an alternative naming convention or specify a file |
Thanks for your suggestion. |
Pull Request #854 adds an option for this. I am interested in feedback on e.g.
|
Pull Request #999 is being considered for v3, adds option to override executable file name |
This issue will be resolved when v3.0.0 is released. Available now as a prerelease. See #1001 |
|
If the script a user wants to execute as a subcommand doesn't abide by the naming convention that's documented (like
pm install
looks for scriptpm-install
), the user should be able to specify the script that's to be executed. For example:In
(1)
, commander would assume the same directory as the current file, look for./myinstall
, then if not found, append.js
, resulting in./myinstall.js
.In
(2)
, commander would use the path relative to the current file. No.js
appended since there's already a.js
extension.in
(3)
, commander would use the absolute path. No.js
appended since there's already a.js
extension.The text was updated successfully, but these errors were encountered: