NPM global package installs don't work unless plugin is installed as "nodejs" about asdf-nodejs HOT 13 CLOSED

So i just ran asdf reshim nodejs and global packages now work. What could be the reason? Should i open an issue for it?

from asdf-nodejs.

Are you supposed to run asdf reshim nodejs after installing a global package? Or is that supposed to be happening automatically somehow?

from asdf-nodejs.

oh man! - glad this is here, has held me up for the better part of an hour tracking down what the issue is.
basically make sure plugin-add as "nodejs" and it just works

asdf plugin-add nodejs https://github.com/asdf-vm/asdf-nodejs.git

Love having ONE version manager for ruby, node, erlang, elixir - thanks a lot :)

from asdf-nodejs.

Re-shimming does not work for me, under OS X.

I installed create-react-native-app via:

npm i -g create-react-native-app

in a .tool-versionsed directory.

• which node and which npm show I'm running the asdf bins.
• npm list -g shows it installed in the proper asdf lib directory.
• npm bin shows only the local node_modules/.bin directory.
• The binary for create-react-native-app is in the asdf installs directory.

Hrm. I'm leaving the above for completeness--the only thing that isn't working is zsh executable auto-complete: if I type the full command name it runs--but not sure how.

from asdf-nodejs.

@faraazahmad I think your error is a separate bug - it might be better off in a new Github issue.

from asdf-nodejs.

Okay, thanks! Hopefully that'll work for me too.

from asdf-nodejs.

This just bit me as well. Seems like the postinstall script could guess the plugin name by looking at the installation directory. Unfortunately I'm not a competent enough Bash scripter to add that in. I changed my plugin's name for now, but it wasn't quite as seamless of an experience as I might have hoped. Also, if ASDF lets you install plugins under any name, perhaps it could/does inject that name into the shell script's environment so it can be used in commands, as is done here.

Either way, only a minor wrinkle. Nice project.

from asdf-nodejs.

Took me half an hour of head scratching to find out why it was failing. Thanks. Be nice to get this updated! Why do you even need to name plugins? Can't they just pick up the name from the plugin...

from asdf-nodejs.

@SoreGums i did the following

asdf plugin-add nodejs https://github.com/asdf-vm/asdf-nodejs.git
asdf install nodejs 9.5.0

But the problem still remains. for example, when i globally install browser-sync i get this

npm WARN lifecycle The node binary used for scripts is /home/faraaz/.asdf/shims/node but npm is using /home/faraaz/.asdf/installs/nodejs/9.5.0/bin/node itself. Use the `--scripts-prepend-node-path` option to include the path for the node binary npm was executed with.

from asdf-nodejs.

@axelson I just ran it once and everything now works as I expect it to, I never had to re run that since.

from asdf-nodejs.

@bsedat is this still an issue?

from asdf-nodejs.

@bsedat can you see if this PR fixes your issue? #150

from asdf-nodejs.

Closing since I think #150 fixed this.

from asdf-nodejs.