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

nodenv version-name doesn't recognize this plugin #25

Closed
rmm5t opened this issue Feb 16, 2018 · 2 comments
Closed

nodenv version-name doesn't recognize this plugin #25

rmm5t opened this issue Feb 16, 2018 · 2 comments

Comments

@rmm5t
Copy link

rmm5t commented Feb 16, 2018

package.json has engines.node specified:

$ cat package.json 
{
  "engines": {
    "node": "6.10.3",
    // ...

node -v then behaves as expected:

$ node -v
v6.10.3

However, node version (and node version-name) do not behave as expected (they are returning my globally set version):

$ nodenv version
8.9.4 (set by /Users/i2190/.nodenv/version)

$ nodenv version-name
8.9.4
@rmm5t
Copy link
Author

rmm5t commented Feb 16, 2018

I should also add some context as to why I care about this discrepancy. I keep my current node version in my bash prompt at all times, and the prompt relies on nodenv version-name.

@hurrymaplelad
Copy link
Contributor

Thanks for the heads up! PR with fix is up.

hurrymaplelad added a commit that referenced this issue Feb 25, 2018
Switch to version hooks. Fixes #25.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants