<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta http-equiv="Content-Type" content="text/xhtml; charset=utf-8"> </head> <body> <div style="font-family:sans-serif"><div style="white-space:normal"> <p dir="auto">On 28 Oct 2016, at 6:49, Graham Heath wrote:</p> <p dir="auto"></p></div> <div style="white-space:pre-wrap"><blockquote style="border-left:2px solid #777; color:#777; margin:0 0 5px; padding-left:5px"><div dir="auto">For NVM to keep multiple versions in the path it adds ~/.nvm/nvm.sh to your </div><div dir="auto">.bash_profile, which interns amends the "default nvm-node path" to PATH. </div><div dir="auto">Like this, `which node` will return something like </div><div dir="auto">"/Users/______/.nvm/versions/node/v6.2.2/bin/node". </div><div dir="auto"> </div><div dir="auto">I could simply add that path to TM_PATH, but if node versions change, </div><div dir="auto">TextMate will continue using the old version (or worse). </div><div dir="auto"> </div><div dir="auto">I’m sure some of you are running into this problem. What have you done to </div><div dir="auto">solve it? </div></blockquote></div> <div style="white-space:normal"> <p dir="auto">The best way to handle these things is by using symbolic links, so you would have a <code style="background-color:#F7F7F7; border-radius:3px; margin:0; padding:0 0.4em" bgcolor="#F7F7F7">current</code> link pointing to the version you wish to use, and you can add that to <code style="background-color:#F7F7F7; border-radius:3px; margin:0; padding:0 0.4em" bgcolor="#F7F7F7">PATH</code>, then no shell script is required to be executed by apps that want to access the current node.</p> <p dir="auto">If NVM does not provide such links, I would make it a suggestion.</p> </div> </div> </body> </html>