[BUG] npm run ignores INIT_CWD

[hinell]

Is there an existing issue for this?

• I have searched the existing issues (found issues)
• A relevant, but unfixed issue: [BUG] INIT_CWD missing in v7 #2033

Current Behavior

INIT_CWD is ignored by npm run command.

Expected Behavior

As it follows from the npm run help page (assuming it's still relevant):
[...] If you want your script to use different behavior based on what subdirectory you're in, you can use the INIT_CWD environment variable, which holds the full path you were in when you ran npm run. [...] ^[0]

Steps To Reproduce

Run the following in zsh/bash.
What it does:

1. Creates /tmp/test-npm-cwd subdir with package.json
2. $ npm run echo from the parental /tmp with INIT_CWD set up to tmp/test-npm-cwd

[[ -d /tmp/test-npm-cwd ]] || mkdir /tmp/test-npm-cwd
cd /tmp/test-npm-cwd
tee package.json <<-EOL
{
        "name": "test-package",
        "scripts": {
                "echo": "echo $INIT_CWD"
        }
}
EOL
cd ..
INIT_CWD="/tmp/test-npm-cwd" npm run echo

The output:

....
npm ERR! enoent ENOENT: no such file or directory, open '/tmp/package.json'

Environment

• OS: Kubuntu 20.1
• Node: v16.4.2
• npm: 7.18.1

[nlf]

Scripts are run from the root of the package folder, regardless of what the current working directory is when npm run is called. If you want your script to use different behavior based on what subdirectory you're in, you can use the INIT_CWD environment variable, which holds the full path you were in when you ran npm run.

INIT_CWD isn't meant to allow you to force a directory, it's a read-only variable used so that you can determine what directory the command was run from in your shell. to run an npm script from another directory, you should try npm --prefix /tmp/test-npm-cwd run echo