-
Notifications
You must be signed in to change notification settings - Fork 32
update from v4.4.5 -> v4.4.7 fails without error #20
Comments
@gr2m Try closing and reopening the installer. I experienced the same thing, and it seems that it's not updating the version after installation. |
that was my very first run ^^ Restarted the installer, same result. I also get a prompt to enter my sudo password, not sure if that’s intended. Happy to leave my node version as is for some time and help debugging the issue |
@gr2m Do you use a version manager like nvm? You can also check your PATH to ensure something isn't resolving node before the vanilla install. Another thing to do is check the version of the node binary in /usr/local/bin. |
Yes, I use
|
@gr2m Oh cool. Yep, I believe it is. The node installer is going to update the binary in /usr/local/bin, not where nvm is installing. And, if your PATH, is anything like mine, the nvm directories are at the front, and therefore resolve |
yeah I can confirm that the node at
Maybe let’s update the README unless you have an idea how to make it work with |
@gr2m What happens if you |
|
I’m okay closing this now in favor of #19. Thanks folks! |
I love the idea for a native app to install Node :)
I just gave it spin. It showed me correctly that my node version is out of date and I could press the update button. And it seemed to have worked, but after it’s done it reverts to the same view again
Here is what the logs say:
The text was updated successfully, but these errors were encountered: