You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently I'm using nvm to manage my installed node versions and I use the stable release. One of my use cases is that I use linters that Sublime Text looks for, each time the stable release updates (say from 4.1.0 to 4.1.1) there's a new version folder and I have to update the path Sublime Text looks at for the linter, if there were a symlink for stable I could just point to it like this
So, first, "stable" is not a concept that exists anymore. All versions of things that follow semver are stable, so io.js, and node 4.0 and later, are always "stable".
As to your primary request: this has been tried before - however, nvm requires a shell environment. It's simply not appropriate to use it in an editor/IDE. See #734, #499, #355, #89.
I understand manually updating npm bin -g in your editor is annoying, but since nvm is not for using a system-wide version of node, there's not a great solution here, unless you can get Sublime to actually source nvm, nvm use node, and then use the resulting npm bin -g or PATH.
Currently I'm using nvm to manage my installed node versions and I use the stable release. One of my use cases is that I use linters that Sublime Text looks for, each time the stable release updates (say from 4.1.0 to 4.1.1) there's a new version folder and I have to update the path Sublime Text looks at for the linter, if there were a symlink for stable I could just point to it like this
The text was updated successfully, but these errors were encountered: