If --package is specified, "@version" should be parsed on that (and only that) about npx

[zkat]

@stuartpb Everything in this issue has (I believe) been implemented as of [email protected]. Thanks for all the ideas! Please do keep them coming. I'll close this issue in particular, though. (and if what you described here doesn't work, it might be a bug, and worth fixing).

[zkat]

Thanks for the suggestion! This was almost exactly what I was doing already buuuut it works now:

This'll be included when I actually release npx. To be clear: I split out everything after <command> and it is interpreted entirely by <command> at that point. Only things left of the command are parsed by npx.

[stuartpb]

👍

Is -- to explicitly signify that the next argument is <command> implemented?

[zkat]

@stuartpb oh. No, not that. I don't think I would do that. The first non-option argument is always interpreted as a command, and it will be used exactly as-is if you provide a -p option. npx itself accepts no variadic argument, so the parser is able to disambiguate this easily enough.

Therefore, npx -p $mypackage@$myversion $@ will be interpreted the way you're describing, unless I misunderstood something.

[stuartpb]

The first non-option argument is always interpreted as a command, and it will be used exactly as-is if you provide a -p option. npx itself accepts no variadic argument, so the parser is able to disambiguate this easily enough.

Well, no, because you can have a command with the same name as an option. It's perfectly valid to have a bin script called -c - it might not be advisable (due to the potential confusion in scenarios just like this), but it can make sense in certain contexts (for instance, for a package that, itself, uses scripts for arguments to the script itself - imagine a project that ran its crispify script when called as foobar crispify, then wanted to add foobar -c as a variant alias for drop-in intercompatibility with a similar tool). Without -- to signal "the next argument is the beginning of the command", there's no way to distinguish this unambiguously.

[stuartpb]

Illustrated:

npx -p foo -c 'require("alert")(1)'
# executes 'require("alert")(1)' in an npm run-script environment

npx -p foo -- -c 'require("alert")(1)'
# runs the script '-c' with 'require("alert")(1)' as its first argument

[stuartpb]

💯