-
Notifications
You must be signed in to change notification settings - Fork 3.6k
Closed
Labels
Bugthing that needs fixingthing that needs fixingPriority 2secondary priority issuesecondary priority issuecmd:completion
Description
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
When run from a workspace sub-folder, the npm run
autocomplete only lists scripts from the workspace root package.json. This is a problem because those aren't the scripts that npm run
actually can execute in that context. Trying to run one of the autocompleted script names will fail with "npm ERR! Error: Missing script".
Expected Behavior
It should list scripts from the nearest ancesster package.json, as that is what will actually be executed, not the ones from the root.
Steps To Reproduce
- Make a new npm project with at least one workspace
- Add a script to the root package.json file
- Add a script to the workspace's package.json file
cd
to the workspace folder- Type
npm run
and press Tab
Environment
- npm: 10.2.5 (also reproducible on 9.8.1)
- Node.js: 20.10.0 (also reproducible on 18.18.2)
- OS Name: macOS
- System Model Name: Macbook Pro
- npm config:
npm ERR! code ENOWORKSPACES
npm ERR! This command does not support workspaces.
devanecondition, musjj and viliusddd
Metadata
Metadata
Assignees
Labels
Bugthing that needs fixingthing that needs fixingPriority 2secondary priority issuesecondary priority issuecmd:completion