[BUG] Passing CLI arguments via a Node scripts no longer works

[JPStrydom]

Is there an existing issue for this?

• I have searched the existing issues

This issue exists in the latest npm version

• I am using the latest npm

Current Behavior

With the following index.js NodeJS file in the root of a new clean NodeJS project:

console.log(process.argv.slice(2));

I get the following output when I run node ./index.js -test-arg test-arg-value:

[ '-test-arg', 'test-arg-value' ]

When I add an NPM script with:

  ...
  "scripts": {
    "arg-test": "node ./index.js",
    ...

and then run it with either of the following:

• npm run arg-test -- -test-arg test-arg-value,
• npm run arg-test -test-arg test-arg-value,
  I simply get:

[ 'test-arg-value' ]

This leaves me unable to run CLI tools, such as Yargs, via NPM scripts like we used to be able to.

Expected Behavior

When using NPM to compose reusable scripts, CLI arguments should still be supported - which enables the use of CLI tools such as Yargs

Steps To Reproduce

1. Using the latest NodeJS (20.12.0) and the latest NPM (10.5.2)
2. With an index.js file in the root of a new NodeJS project containing the following:
   • index.js:

     console.log(process.argv.slice(2));

3. Run the file with node ./index.js -test-arg test-arg-value
4. See the expected output: [ '-test-arg', 'test-arg-value' ]
5. Add an NPM script to the package.json file to run the file:
   • package.json:

     "type": "module",
     "scripts": {
       "arg-test": "node ./index.js"
     }

6. Run the file with either of the following:
   • npm run arg-test -- -test-arg test-arg-value,
   • npm run arg-test -test-arg test-arg-value,
7. See the incorrect output [ 'test-arg-value' ]

Notes:

• I'm using module type Node with "type": "module", in the package.json file.
• I've tried with Bash terminal but did not experience this issues. Only PowerShell and Command had this error.

Environment

• npm: 10.5.2
• Node.js: 20.12.0
• OS Name: Windows 11 Pro 23H2 (22631.3447)
• System Model Name: Dell G15 5510
• npm config:

; "user" config from C:\Users\jp.strydom\.npmrc

//registry.npmjs.org/:_authToken = (protected) 

; node bin location = C:\Program Files\nodejs\node.exe
; node version = v20.12.0
; npm local prefix = C:\Data\Development\XXX\XXX
; npm version = 10.5.2
; cwd = C:\Data\Development\XXX\XXX
; HOME = C:\Users\XXX
; Run `npm config ls -l` to show all defaults.

[JPStrydom]

It seems like adding another argument delimiter (--) fixes the issue.

i.e. running with npm run arg-test -- -- -test-arg test-arg-value causes the correct behavior. Not sure when Microsoft changes this, because only using on delimiter definitely used to work.

[noseratio]

I'm also affected by this issue. It appears to be a shenanigan of both PowerShell and NPM working together. Node.js is not involved. A proof:

package.json:

{
  "name": "cli-test",
  "scripts": {
    "showcli": "echo",
    "showbatcli": "test.cmd"
  }
}

test.cmd:

@echo %*

• Running the following from PowerShell fails (--arg=value is lost):

PS C:\temp\cli-test> npm run showcli -- command --arg=value

> cli-test@1.0.0 showcli
> echo command

command

• This also fails:

PS C:\temp\cli-test2> npm run showbatcli -- command --arg=value

> showbatcli
> test.cmd command

command

• Via CMD.exe, it works:

PS C:\temp\cli-test> cmd /c npm run showcli -- command --arg=value

> cli-test@1.0.0 showcli
> echo command --arg=value

command --arg=value

• Running test.cmd without NPM also works:

PS C:\temp\cli-test2> ./test.cmd -- command --arg=value
-- command --arg=value

[noseratio]

Digging more into this, the problem appears to be with "C:\Program Files\nodejs\npm.ps1", which gets invoked when we type npm from a PowerShell prompt on Windows.

OTOH, running the npm.cmd ("C:\Program Files\nodejs\npm.cmd") explicitly works ok, a workaround I'm settling on for now:

PS C:\temp\cli-test2> npm.cmd run showbatcli -- command --arg=value

> showbatcli
> test.cmd command --arg=value

command --arg=value

[lukekarrys]

@noseratio Can you test with the latest branch which now includes new Powershell scripts as of 5230647?

Confirmed this does not fix the issue.