[BUG] --scr and some other npm config variables not allowed

Is there an existing issue for this?

[X] I have searched the existing issues

This issue exists in the latest npm version

[X] I am using the latest npm

Current Behavior

emil@Emils-MBP:~/Desktop/npm-run-flag-test$ npm start --scr=foo

> npm-run-flag-test@1.0.0 start
> env | grep npm_config_s | sort

npm ERR! code ENOENT
npm ERR! syscall spawn foo
npm ERR! path /Users/emil/Desktop/npm-run-flag-test
npm ERR! errno -2
npm ERR! enoent spawn foo ENOENT
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent 

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/emil/.npm/_logs/2023-06-30T14_37_13_384Z-debug-0.log

The above output can also be seen when using --scri, --scrip, and --script too.

Expected Behavior

emil@Emils-MBP:~/Desktop/npm-run-flag-test$ npm start --scripty=foo

> npm-run-flag-test@1.0.0 start
> env | grep npm_config_s | sort

npm_config_scripty=foo
npm_lifecycle_script=env | grep npm_config_s | sort

I would expect the above output, but with scr|scri|scrip|script in lieu of scripty.

Steps To Reproduce

On npm 8 (and 9)...

With the following package.json...

{
  "name": "npm-run-flag-test",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "start": "env | grep npm_config_s | sort"
  },
  "author": "",
  "license": "ISC"
}

Running any of the following:

npm start --scr=foo
npm start --scri=foo
npm start --scrip=foo
npm start --script=foo

... Yields the above error

Environment

npm: 9.5.1
Node.js: 18.16.1
OS Name: macos Monterey 12.6.6
System Model Name: MacBook Pro (16-inch, 2021)

npm config:


; copy and paste output from `npm config ls` here
; node bin location = /Users/emil/.nvm/versions/node/v18.16.1/bin/node
; node version = v18.16.1
; npm local prefix = /Users/emil
; npm version = 9.5.1
; cwd = /Users/emil
; HOME = /Users/emil
; Run `npm config ls -l` to show all defaults.

npm / cli