-
Notifications
You must be signed in to change notification settings - Fork 3.7k
Closed
Labels
Bugthing that needs fixingthing that needs fixingCannot Reproduceplatform:windowsis Windows-specificis Windows-specific
Description
Is there an existing issue for this?
- I have searched the existing issuesTo pick up a draggable item, press the space bar. While dragging, use the arrow keys to move the item. Press space again to drop the item in its new position, or press escape to cancel.
This issue exists in the latest npm version
- I am using the latest npmTo pick up a draggable item, press the space bar. While dragging, use the arrow keys to move the item. Press space again to drop the item in its new position, or press escape to cancel.
Current Behavior
Execute the following Powershell command:
& npm @("run", "ci")
This works in Node 20 LTS / npm 10.1.0. In Node 22 LTS / npm 10.9.2, the following error is shown:
Unknown command: "run ci"
To see a list of supported npm commands, run:
npm help
It seems that npm failed to parse the space and passes "run ci" to cmd-list.js
deref
. Workaround using & npm.cmd @("run", "ci")
is also an option, so this could be an issue with npm.ps1
?
Expected Behavior
The command should work as before (npm 10.1.0)
Steps To Reproduce
- Node 22 LTS / npm 10.9.1
- Run
& npm @("run", "ci")
in Powershell - Got unknown command error
Environment
- npm: 10.9.2
- Node.js: v22.14.0
- OS Name: Windows 11
- npm config:
; "builtin" config from C:\Program Files\nodejs\node_modules\npm\npmrc
prefix = "C:\\Users\\Adrian Godong\\AppData\\Roaming\\npm"
; "user" config from C:\Users\Adrian Godong\.npmrc
cache = "C:\\Users\\Adrian~1\\AppData\\Roaming\\npm-cache"
; "project" config from C:\Users\Adrian Godong\Desktop\pancore\develop\.npmrc
install-links = false
legacy-peer-deps = true
registry = "**redacted**"
; node bin location = C:\Program Files\nodejs\node.exe
; node version = v22.14.0
; npm local prefix = C:\Users\Adrian Godong\Desktop\**redacted**
; npm version = 10.9.2
; cwd = C:\Users\Adrian Godong\Desktop\**redacted**
; HOME = C:\Users\Adrian Godong
; Run `npm config ls -l` to show all defaults.
Metadata
Metadata
Assignees
Labels
Bugthing that needs fixingthing that needs fixingCannot Reproduceplatform:windowsis Windows-specificis Windows-specific
Type
Projects
Milestone
Relationships
Development
Select code repository
Activity
milaninfy commentedon Mar 28, 2025
This is working as expected on my end on the latest npm@11.2.0. Also you can run
npm ci
for clean install.For your use case could you please share the full logs and complete powershell output ?
adriangodong commentedon Mar 28, 2025
Can also repro the issue on npm 11.2.0.
I have a custom script called ci. Same issue with other commands below.
I'm not sure how to get the full logs.
milaninfy commentedon May 7, 2025
You can try updating your powershell, or there might be some powershell related settings/config you can tweak
here is my output
milaninfy commentedon May 9, 2025
Closing this as it's not reproducible as shown in the output. If you are doing things differently or have found any other way to reproduce this issue, feel free to reopen the issue.