Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Drop nvm use and rename prompt_nvm to prompt_node #135

Open
3 tasks
faceleg opened this issue Apr 20, 2016 · 2 comments
Open
3 tasks

Drop nvm use and rename prompt_nvm to prompt_node #135

faceleg opened this issue Apr 20, 2016 · 2 comments

Comments

@faceleg
Copy link
Contributor

faceleg commented Apr 20, 2016

This issue is for discussion and planning.

As proven in #133, nvm is not required to get the current environment's node version.

@drwpow
Copy link

drwpow commented Jan 1, 2017

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.

@FrederickGeek8
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants