Development record
npm's value-taking config flags and global options are not in the runner value-flag lists, so their value is read as the program: npm exec --registry <url> kill-port 3000, --cache <dir>, --userconfig <file>, and a global option before the subcommand (npm --prefix . exec kill-port 3000) read the value or the option as the program and only warn as an unrecognised launcher where npm exec kill-port 3000 blocks.
issueopennitpickiss-2610142235000193
npm's value-taking config flags and global options are not in the runner value-flag lists, so their value is read as the program: npm exec --registry <url> kill-port 3000, --cache <dir>, --userconfig <file>, and a global option before the subcommand (npm --prefix . exec kill-port 3000) read the value or the option as the program and only warn as an unrecognised launcher where npm exec kill-port 3000 blocks.
Frontmatter
| id | iss-2610142235000193 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | nitpick |
.abcd/work/issues/open/iss-2610142235000193-npm-s-value-taking-config-flags-and.md
open on GitHub ↗ · commit history ↗