Global installs not being found in npm@7

[jonatan-ivanov]

Globally installed packages can't be executed and the command fails with command not found.
Workaround: export PATH="$PATH:$(asdf where nodejs)/.npm/bin" (though I guess this won't work with version change)

[augustobmoura]

Try running asdf rehism nodejs after npm install -g, .npm/bin should not be in the path (not without workarounds) this is not how asdf works internally, the problem with adding $(asdf where nodejs) to PATH is that the value can change from context to context. Instead asdf creates a shim for every executable in .npm/bin so that it can point to the correct nodejs version

This is caused by a npm@7 regression, as of now we will need to manually run asdf reshim nodejs after every global install, I'm currently researching a way of not relying in .hooks to auto reshim

[augustobmoura]

Okay, so I pushed a new mechanism for auto-reshimming that works by wrapping the npm command and only reshimming when necessary. Instead of relying on npm node_modules/.hooks.

@jonatan-ivanov, can you update your asdf-nodejs and test if everything is working as intended?

[jonatan-ivanov]

@augustobmoura Thanks for looking into this. I uninstalled and installed a package, both times I see the message: Reshimming asdf nodejs... and this works now, thank you! :)

[igorcafe]

I installed asdf using AUR and I'm still having this issue, even after reopening my terminal.

issue.mp4

[WorstPractices]

I installed asdf using AUR and I'm still having this issue, even after reopening my terminal.

did you get this straightened out? i have the same issue.

[rroslaniec]

same here

[iloveitaly]

running into this as well, I wonder if it has something to do with the global vs local asdf nodejs version. If I have more time to investigate further, I'll reach out.

[TamasBarta]

@iloveitaly, if the global one was used to install the npm package instead of the asdf managed version, I believe you should still get the command in the path, but not managed by asdf. I start to believe that npm itself is faulty, because I tried setting asdf's nodejs to system, and I just have no way of getting any command to work. The workaround mentioned here also doesn't work for me, because that directory has no commands either. (export PATH="$PATH:$(asdf where nodejs)/.npm/bin") I'm confused.