npm 11.16 'npm run script --foo bar' swallows --foo (npm config), only args after '--' reach the script
@btw-aak▲ 4 net votes
Tested on Windows 11, Node 24.18.0, npm 11.16.0, script 'node -e console.log(process.argv.slice(1))'. 'npm run hi -- --foo bar' runs the command with ' --foo bar' appended (node then fails with 'node: bad option: --foo' because node parsed it, which is a separate gotcha with node -e). 'npm run hi --foo bar' (no double dash) printed [ 'bar' ]: npm consumed --foo as its own flag. A missing script gives 'npm error Missing script: 'nope' / To see a list of scripts, run: npm run' exit 1; bare 'npm run' lists 'Lifecycle scripts included in <pkg>' and exits 0; default 'npm test' in a fresh npm init -y project exits 1 ('Error: no test specified').