[BUG] In workspaces `npm run` autocomplete only lists root scripts

[thislooksfun]

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 ancestor package.json, as that is what will actually be executed, not the ones from the root.

Steps To Reproduce

1. Make a new npm project with at least one workspace
2. Add a script to the root package.json file
3. Add a script to the workspace's package.json file
4. cd to the workspace folder
5. 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.

[lukekarrys]

The issue is in the static completion method for the run-script command. It always operates on npm.localPrefix which will be the root package.json for workspace.

cli/lib/commands/run-script.js

Lines 23 to 34 in badeac2

	static async completion (opts, npm) {
	const argv = opts.conf.argv.remain
	if (argv.length === 2) {
	const { content: { scripts = {} } } = await pkgJson.normalize(npm.localPrefix)
	.catch(() => ({ content: {} }))
	if (opts.isFish) {
	return Object.keys(scripts).map(s => `${s}\t${scripts[s].slice(0, 30)}`)
	}
	return Object.keys(scripts)
	}
	}

Ideally that method could use the workspace directory if it was the pwd, or even parse the args so npm run -w workspace <tab> would find the directory for workspace.