only available in 32bit bug.

[rahulroy9202]

[vkbansal]

It's not a bug. You are typing wrong commands.

You must use

nvm install 0.10.32

and not

nvm install 10.32

[rahulroy9202]

Hi. Sorry I didn't include any context in the bug report.

I meant to say that in case of such an error, it should say unrecognized version, instead of saying that the no existent version exists but only in 32bit. (my system is 64bit.).

[vkbansal]

@coreybutler might take a note about it

[coreybutler]

@rahulroy9202. I've merged your changes. While it may be a simple code change, I think this adds value to the overall user experience. Thanks for the PR!

[ublue1024]

[ublue1024]

so what's the problem here?

[coreybutler]

@ublue1024 - The error you're experiencing can be caused by one of two scenarios. First, if you're using an older version of Windows (like XP), it may be missing a native command. See issue #23 and #37 for details.

The other cause is a small bug. If you don't install both the 32-bit and 64-bit versions of a specific node version, it can cause this behavior. The issue has been resolved in the master branch, but I have not and will not release this as a new version... only because my time is too consumed between my day projects and working on the next version of nvm-windows... which already has a fix for this (see the Gitter feed for more detail). In the interim, you can build from source. Another user wrote instructions in the wiki about how to do this.

[ublue1024]

Thanks, my computer is running on Windows 7. I don't know how to build from source, so I prefer to wait for the next version.

[rainabba]

The 'v' prefixing really needs to be standardized. I was dealing with the same because of the inconsistency in prefixing versions with 'v'.