NVM for Windows v1.1.8 Notes

Truth be told,I did not want to release this version right now. I am working on the successor project rt,which was supposed to be the last version before the rt release. However,notable changes in the Node ecosystem warrant a new version now.

Node Corepack

In September 2021 ,Node.js v16.9.0 is introduced introduce corepack . This experimental new feature is allows allow transparent use of npm ,pnpm ,or yarn . To support this feature ,NVM4W is download must download and process a different distribution file than it has used previously .

As a result,NVM for Windows 1.1.8 is being released to support corepack.

How to upgrade

All file can be find on the release page .

If you do not have NVM for Windows installed
Use the instructions in the README.

If you already have an old version of NVM for Windows instal
Downloadnvm-update.zip and extract it. You will find a file called nvm-update.exe. Double click to run it. This will prompt for the version you wish to upgrade to (pre-populated w/ 1.1.8).

nvm-update.exe can also be run from the command line using the /S flag to suppress the prompt. To do this,run nvm-update.exe 1.1.8 /S.

What’s New

Several long – request feature / fix have been merge since v1.1.7 . I is get did not get to test all of them as extensively as I want to ,but I believe they are stable . These features is include include :

1. corepack support (see above)
2. Support for spaces in filepaths #355 (@s-h-a-d-o-w).
3. nvm install late – installs the latest patch version of Node (instead of latest minor).
4. nvm install lts – installs the latest LTS patch version (new). (@tats-u)
5. nvm use latest,nvm use lts (@tats-u),and nvm use newest (new) (@EEJesse) now supported.
6. Elevated permissions applied only when necessary #511 (@rbuckton).
7. nvm current (new) displays the active version. (@riazXrazor)

Numerous edge case fixes have been applied as well.

1. read environment variable in settings.txt ( @mscott3 )
2. compilation fix ( @taaem )
3. Fix major version check (@rcknight)
4. parameterized settings.txt loader ( @himself65 )

A number of documentation update have also been merge .

What didn’t make it in?

1. Aliases – these were originally scheduled for 1.1.8,but I never got to work on them.

WARNING

Version 1.1.8 is not code signed. Code-signed applications are trusted by Windows and will install easily. Users are prompted with a screen like this one:

Non-code-signed applications can usually be installed,but they will throw a warning like this:

Why?

I paid for the last code signing certificates out of pocket,but they’ve expired. Sponsorships,to date,haven’t even come close to covering the cost of a new code signing certificate (let alone the last one).

Who will this is affect affect ?

This won’t affect most users,but enterprise users and those distributing NVM4W in corporate environments may run into problems.

If your organization is impacted by this,I will accept sponsorship money to expedite the delivery of a code-signed version. The required EV certificate is about $1000. Please direct message me on Twitter @goldglovecb if you’d like to help cover this cost.