Upgrade fails with Node.js 5.4.1 and npm 3.5.4

[felixrieseberg]

Upgrade fails with Node.js 5.4.1 and npm 3.5.4

[felixrieseberg]

Hey, I'm so sorry about this - thank you for reporting. I'll try to reproduce and fix the issue.

[nazrhyn]

👍

I did a clean install of NodeJS 5.4.1, then npm install -g npm-windows-upgrade. Same error.

Edit: I tried following @atom0s's instructions to do a repair then try the upgrade again. It does seem to have worked, but this was the output:

$ ./npm-windows-upgrade
npm-windows-upgrade 1.2.0
? This tool will upgrade npm. Do you want to continue? Yes
? Which version do you want to install? 3.5.4
Upgrading... -Error:  npm
Error:
Error:  WARN
Error:  ENOENT ENOENT: no such file or directory, open 'C:\Program Files\nodejs\package.json'

Error:  npm
Error:   WARN EPACKAGEJSON nodejs No description

Error:  npm
Error:   WARN EPACKAGEJSON nodejs No repository field.

Error:  npm
Error:   WARN EPACKAGEJSON nodejs No README data

Error:  npm
Error:   WARN EPACKAGEJSON nodejs No license field.



Upgrade finished. Your new npm version is 3.5.4. Have a nice day!

[felixrieseberg]

Again, thanks for reporting - I confirmed what is going on here. Interestingly, if you do the following, not all module are installed correctly:

• Install Node 5.4.1
• Go to C:\Program Files\nodejs (where npm.bat lives)
• Run .\npm install npm@latest

I'll try to figure out what's going on, but I'm afraid this might be an upstream issue in npm (not that that would be in any way better).

[felixrieseberg]

I confirmed that this is an upstream issue - [email protected] and below should be fine. I'll think about a way to warn users about issues like these.

[nazrhyn]

Cool. Good detective work; thanks.

[felixrieseberg]

Closed in npm.