1.1.10

[coreybutler]

This is primarily a bug fix release.

Many users have requested UAC prompts be reinstated. NVM4W attempts to run commands without elevation. If this succeeds (i.e. developer mode is enabled and active), the process continues without prompts. If a command fails, an attempt to run it with elevated privileges will trigger the UAC prompt.

What's Changed

• Update error message when missing version argument. Fixes nvm use alone with .nvmrc always returns "Invalid version." #722. by @0liver in Update error message when missing version argument. Fixes #722. #731
• Fix README.md incorrect element close by @WORMSS in Fix README.md incorrect element close #768
• Allow nvm use to be called with the part of the semver by @vladonemo in Allow nvm use to be called with the part of the semver #709
• Refactor/minor typo fixed in comments by @SayefReyadh in Refactor/minor typo fixed in comments #806
• Fix missing DisplayVersion registry key for nvm.iss by @awdr74100 in Fix missing DisplayVersion registry key for nvm.iss #796
• Update inno setup config to correctly report version (fix Nvm not reporting version after installed #851) by @psnitil in Update inno setup config to correctly report version (fix #851) #868

New Contributors

• @0liver made their first contribution in Update error message when missing version argument. Fixes #722. #731
• @WORMSS made their first contribution in Fix README.md incorrect element close #768
• @vladonemo made their first contribution in Allow nvm use to be called with the part of the semver #709
• @SayefReyadh made their first contribution in Refactor/minor typo fixed in comments #806
• @awdr74100 made their first contribution in Fix missing DisplayVersion registry key for nvm.iss #796
• @psnitil made their first contribution in Update inno setup config to correctly report version (fix #851) #868

A few PR's were manually added, since merging them proved to be difficult after other changes. So, I'd like to give a special thanks to the following folks whose PR's were manually included (but not recognized in the changelog):

• @thengoster for Added console messages indicating to the user that npm installed successfully #784
• @craig-et for altered runElevated to accept command and args fixing the elevation bug #828 (which brought UAC prompts back)

Full Changelog: 1.1.9...1.1.10

---

This discussion was created from the release 1.1.10.

[WORMSS]

❤️
Nothing more to say.

[kdpuvvadi]

will you be adding executable installer in the assets instead of zip for the latest release?

[coreybutler]

The zip contains the executable installer. It's always been packaged in a zip file because most company firewalls block the direct download of exe files.

[kdpuvvadi]

Yes, i get it for corporate env but we also use in the home. including exe would be nice for someone who needs it (it was included in the 1.1.9).

[coreybutler]

@kdpuvvadi I'm still not very clear why unzipping the file is a problem, but I added the executable to the 1.1.10 release for those who want to download it directly.

[kdpuvvadi]

unzipping a file is not that big of deal. We've this internal automation script that check for updates and installs them. we included nvm-windows before last release(1.1.9) and after 1.1.10, it broke on bunch of the boxes. So, We've uploaded extracted file temporarily on our file server. Our chief tech insisted on url from source. Then i've direct yesterday and added unzipping to script.

We are migrating to winget internally. So, that won't be any issue as of today test repo is working. I've mentioned your rt project to concerned team, they are interested on that but might expect support.

[coreybutler]

@kdpuvvadi Runtime (rt) will have a core free version and a commercial supported version. The NVM4W winget installation is not an official installation, but Runtime will have an official winget installation option.

If your team is interested (or anyone else reading this), the best way to be notified of Runtime updates/releases is to fill out the survey, which has a place for an email address to be notified. I'll also make an announcement on Twitter (@goldglovecb and @author_io). I'm hoping to have time to setup a formal website for Runtime over the holidays. In the meantime, the Runtime Wiki Page will be updated as progress is made.

[bhhoang818]

what was wrong

[coreybutler]

Did you download the installer or the updater from https://github.com/coreybutler/nvm-windows/releases/tag/1.1.10? Both of these installers produce version 1.1.10.

I have seen this with users who download from non-official sources. There was a problem with a version number in an older version of NVM4W (I think in 1.1.9), which was corrected within 2-3 days, but that was long enough for some of the mirrors to downloaded the "bad" version (they never updated).

[Jewgah]

Hi everyone, I've seen on a stackoverflow post (link here) that node and npm need to be uninstalled manually before installing nvm, is that true or do latest versions take care of this issue ?

[alielmajdaoui]

2 security vendors and no sandboxes flagged this file as malicious!

[0liver]

There's already an issue tracking this: #882.

[alielmajdaoui]

There's already an issue tracking this: #882.

My bad! Thanks for the link

[coreybutler]

This resolved itself.

[0liver]

How do we push that latest version to https://community.chocolatey.org/packages/nvm?

[Kristhian92]

fork/exec C:\Users\Usuario\AppData\Roaming\nvm\elevate.cmd:
Hello I get this error: The system cannot find the specified file.
How to solve it?

[coreybutler]

This file ships with the installer and the setup. If you installed it from another source, then I don't know why it would be missing. You can download it manually from https://github.com/coreybutler/nvm-windows/tree/master/bin.

[Kristhian92]

The file is fine, it appears in the folder but when I click on it nothing appears and when I open it in the terminal I get that error.