nvm-windows | js version management utility for Windows | Runtime Evironment library

Apparently this is the new way npx behaves per github issue

Seems @jcollum ran across the very same issue per this stackoverflow question.

As it has been said here, just execute the following line and make sure it is git-tracked to solve the problem.

I ran across this npm bug report npm ci behaves incorrectly with some version numbers
which had a link to the archived post
npm prune –production (after npm ci only) erroneously uninstalls regular dependency

So I started looking at how the @dealertrack package was specified.

I changed

My walkaround to this problema is detailed in the update 2, but it's basically what I explained here: I’ve seen in this link (Error: C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\MSBuild\15.0\Bin\MSBuild.exe failed with exit code: 1) that some people tried a downgrade in the node version, I was using originally the version 12 and some say that with version 10 should work. After that I can perform the four steps provided in the answer:

To solve the problem use nw u [version] like:

Uninstall and reinstall nvm. Make sure to do this before reinstalling:

Uninstall existing node Please note, you need to uninstall any existing versions of node.js before installing NVM for Windows. Also delete any existing nodejs installation directories (e.g., "C:\Program Files\nodejs") that might remain. NVM's generated symlink will not overwrite an existing (even empty) installation directory.

Uninstall existing npm You should also delete the existing npm install location (e.g. "C:\Users\AppData\Roaming\npm"), so that the nvm install location will be correctly used instead. Backup the global npmrc config (e.g. C:\Users\AppData\Roaming\npm\etc\npmrc), if you have some important settings there, or copy the settings to the user config C:\Users.npmrc.