[QUESTION] Is there support for following module resolution paths?

[arciisine]

What / Why

I'm currently running into an issue, with a monorepo, in that I want npx to pick up the executable in the parent directory, instead of just looking at the current directory. I'm not sure if I'm missing something, but running npx eslint in the sub package folder of the monorepo cannot find eslint in the parent node_modules directory.

The node Module documentation, https://nodejs.org/api/modules.html, specifies the load order for modules, including parents. Executing require.resolve.paths('') should return the list of all available paths that are searched on a require.

Where

This should be how require operates currently today.

[JoeAlamo]

I'm in same situation

Please see
zkat/npx#210
zkat/npx#222

[charlie-axsy]

Assuming you're like me and bumping into problems with Lerna hoisting into a root level .bin directory. I wonder if Lerna itself should be creating symlinks in the package/node_modules/.bin rather than assuming tooling will look upwards to find binaries

[charlie-axsy]

Aha, I found that Lerna was not symlinking eslint into my packageX/node_modules/.bin directories because it was not specified in "devDependencies". With the symlink in place, npx eslint now works as I expected, without trying to install eslint from the registry each time.