This repository has been archived by the owner on Sep 11, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 149
Error after upgrade ... but upgrade seems successful #11
Labels
Comments
Actually ... now I am not sure if the update actually worked. Despite what the list command is reporting (see above) doing npm -v returns 2.11.2 |
Closed powershell and re-opened and ran npm-windows-upgrade again and received a different error:
|
Just noticed something that may be relevant to this issue: My node installation is in C:\nodejs But reading the manual solution it sounds like the assumption is node is installed in C:\Program Files (x86)\nodejs |
Actually, I have hopes that the just released version 0.3.2 will fix your issue. Do me a favour and run |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
@felixrieseberg I just updated to version 0.2.3 of npm-windows-upgrade because I was having the same issue described in issue #10
I then ran it (on Windows 8.1 pro) and got this error message:
But despite the error message, it looks like the upgrade happened:
I am new to node and npm so could be just something weird I did to my environment while learning and experimenting but thought I would report it.
The text was updated successfully, but these errors were encountered: