Skip to content

Conversation

@epoweripione
Copy link
Contributor

Hopefully fixes #2914

Copy link
Member

@ljharb ljharb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Rather than just add this default, I'd prefer to figure out which code branch is failing to set the EXIT_CODE properly.

@jerome-benoit
Copy link

I confirm it fixes the issue but @ljharb is right: that is not fixing the root cause and why a not properly initialized variable ends up in a condition check.

Copy link
Member

@ljharb ljharb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

k, i've figured it out - the nvm use result wasn't being captured, and nvm install --lts was triggering that.

Will land and release this soon.

@ljharb ljharb added the installing node Issues with installing node/io.js versions. label Oct 15, 2022
@ljharb ljharb merged commit fe6268c into nvm-sh:master Oct 16, 2022
@wouterds
Copy link

I'm still getting this on 0.39.2 ?

@ljharb
Copy link
Member

ljharb commented Oct 21, 2022

That’s because this fix isn’t in v0.39.2.

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

Labels

installing node Issues with installing node/io.js versions.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

nvm:[:556: unknown condition: -ne / nvm:[:560: unknown condition: -ne / ....

4 participants