volta seems to not handle cli's on npm link correctly

[serapath]

1. I npm link and volta put's /home/<username>/.volta/bin into my $PATH,
2. but the cli is moved into /home/<username>/.volta/ .... .... .... /bin/<cmd>
3. so I assume volta is not adding and updating a symlink
   • e.g. /home/<username>/.volta/bin -> /home/<username>/.volta/ .... .... .... /bin
   • where ... ... ... depends on the current node -v and npm - v
   • and would be, e.g. /tools/image/node/12.14.1/6.13.4 🙂

[serapath]

alternatively, volta should add and maintain the current node -v and npm -v dependent .../bin paths to my $PATH

[charlespierce]

@serapath There's a couple issues to unpack here. First and foremost is that we don't have a good story for npm link / yarn link in general (see #56).

That said, I also think this is a new use-case for npm link that we weren't aware of. I think that will also need to be part of the overall story for supporting npm link, where we either generate a short-term shim or in some other way make a tool that has been linked available to you. We don't modify the terminal's PATH and our approach with volta install is to avoid having things depend on the Node version that you are currently using, so that you don't have to keep re-installing the same tools every time you change Node versions, so it's unfortunately not a simple solution.

[dieeisenefaust]

Same issue here. Had to move back to nvm to be able to be able to troubleshoot an issue with another package's cli.