Prefer local node_modules/.bin? about nodenv

[jasonkarns]

nodenv alters PATH when the output of nodenv init is sourced (or evaled depending on your setup)

So you just need to prepend ./node_modules/.bin to PATH after you've invoked nodenv-init

[jasonkarns]

I have an idea for a plugin to make this possible, but at present it is not. It's not related to nodenv in any way. Local node_modules bins simply aren't on the path, and a non-nodenv installation isn't any different. There are alternatives, however.

1. Add ./node_modules/.bin to your PATH. Though there are security reasons to avoid this.

2. $(npm bin)/coffee will run the local coffee. And npm-bin works anywhere in the project (not just at root).

3. Use npm run-scripts. When an npm script is invoked via npm run foo, npm prepends $(npm-bin) to your PATH. So scripts can invoke any locally installed bin without the need to prefix it.

   "scripts": {
     "compile": "coffee"
   }

   Now npm run compile will use your local coffee.

The complication for making a plugin for this is finding a way to make nodenv aware of all your local node_modules. It can't shim what it doesn't know about. Best I can think of so far, is that the plugin prepends $(npm bin) to the PATH during the exec hook. But this would only work for modules that have been installed globally and are thus shimmed. So for any locally-installed bin, one would need to install it globally as well. Then the global shim would trigger nodenv, and the exec hook could prepend local bin path.

[hurrymaplelad]

Thanks for all the thoughts!

I'm in bucket #1. I've already added ./node_modules/.bin to my path, but I can't give them precedence over globally installed modules which nodenv pretends to my path.

Any thoughts on configuring where in the path the shims are added?

On Feb 11, 2016, at 5:22 AM, Jason Karns [email protected] wrote:

I have an idea for a plugin to make this possible, but at present it is not. It's not related to nodenv in any way. Local node_modules bins simply aren't on the path, and a non-nodenv installation isn't any different. There are alternatives, however.

Add ./node_modules/.bin to your PATH. Though there are security reasons to avoid this.
$(npm bin)/coffee will run the local coffee. And npm-bin works anywhere in the project (not just at root).
Use npm run-scripts. When an npm script is invoked via npm run foo, npm prepends $(npm-bin) to your PATH. So scripts can invoke any locally installed bin without the need to prefix it.

"scripts": {
"compile": "coffee"
}
Now npm run compile will use your local coffee.

The complication for making a plugin for this is finding a way to make nodenv aware of all your local node_modules. It can't shim what it doesn't know about. Best I can think of so far, is that the plugin prepends $(npm bin) to the PATH during the exec hook. But this would only work for modules that have been installed globally and are thus shimmed. So for any locally-installed bin, one would need to install it globally as well. Then the global shim would trigger nodenv, and the exec hook could prepend local bin path.

—
Reply to this email directly or view it on GitHub.

[jasonkarns]

Closing since there's a workaround: