[BUG] npx is ignoring NODE_PATH

[robsmith11]

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

If I run, NODE_PATH=/path/to/my/node_modules npm, I'm able to load all of my locally installed packages, but if i do the same with npx, it does not see any of them and only works with node_modules in the current working directory.

Expected Behavior

If I run, NODE_PATH=/path/to/my/node_modules npm, I'm able to load all of my locally installed packages, but if i do the same with npx, it does not see any of them and only works with node_modules in the current working directory.

Steps To Reproduce

If I run, NODE_PATH=/path/to/my/node_modules npm, I'm able to load all of my locally installed packages, but if i do the same with npx, it does not see any of them and only works with node_modules in the current working directory.

Environment

• npm: 9.6.7
• Node.js: 9.6.7
• OS Name: NixOS
• System Model Name: NixOS
• npm config:

; copy and paste output from `npm config ls` here

[ljharb]

NODE_PATH is highly discouraged and largely deprecated and won’t ever work with ESM; why are you setting it?

[robsmith11]

Because npx also breaks when I make node_modules a symlink. I just want to install my project's dependencies outside of my source directory, but still be able to use npx.

[ljharb]

That’s not really how node works. Deps need to be in node_modules.

[robsmith11]

So everyone just has their source directories polluted with large binaries? I've never used a language / package manager that didn't allow changing the build and install locations. At the very least npm should not be breaking symlinks.

[ljharb]

Yes, and node_modules is always gitignored.