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
Also wanted to add BULLETRAIN_NVM_SHOW, et al work just fine for nodenv (rbenv for Node). It’s not a major issue, but as suggested, naming it something more generic like NODE would be a little more straightforward.
There is a subtlety to this issue. NVM is not required to get node version if NVM is loaded. There can arise a situation when trying to lazy-load plugins for performance enhancement which results in NVM only becoming loaded when a command like node or nvm is executed.
This is something I address in my pull request #274 . One problem with this observation is that if you are trying to lazy-load nvm and were to use a implementation that would just run node --version, then NVM would be loaded into the shell, thus defeating the purpose of lazy-loading.
This issue is for discussion and planning.
As proven in #133, nvm is not required to get the current environment's node version.
The text was updated successfully, but these errors were encountered: