How should I upgrade from 1.1.9 to the current version? #1253
Unanswered
aminomancer
asked this question in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
When I run the installer, it asks me to pick a symlink folder, which by default is
C:\nvm4w\something
. This made me hesitate to go through with the installation, because I have a big house of cards built on top of several years of using v1.1.9 for my work.Right now, my
NVM_SYMLINK
var is set toC:\Program Files\nodejs
, which I think the previous nvm-windows installer set. So, are these the same thing? Is the installer's symlink folder setting going to overwrite this? It's odd because it says this is the folder it will create the symlink in, not the symlink to. I assumed nvm-windows created a symlink atC:\Program Files\nodejs
(explaining why you need to uninstall node versions) and then setsNODE_PATH
toC:\Program Files\nodejs\node_modules
, so that it leads to the folders inNVM_HOME
. Makes sense, that's the usual install path for node. But the new installer shows a path doesn't already exist.So I'm wondering what happens to the existing installation's symlink and env vars. I know it says you can upgrade by just running the installer, but maybe that's only generally true, and not true if you're upgrading from an old enough version. Also, the readme says "💡 As of v1.1.8, there is an upgrade utility that will automate the upgrade process," but it doesn't say how to access this utility. I don't know if that utility is an nvm command, a file in the nvm directory (I did not see any), or built into the installer (it didn't seem to acknowledge I had an existing installation).
In most cases I'd just throw the dice and see what happens, but if something goes wrong and I lose existing node modules or my PATH can't find them, it could cause me real problems. So I'd probably just stay on 1.1.9 to avoid the risk, but I'm getting errors when trying to install recent node versions.
nvm install latest
throws an error, and so does it fail when I specify a recent version number. For example:I assume these bugs are probably resolved in the latest nvm-windows version, so I'd like to upgrade, as long as it's safe to do so.
Beta Was this translation helpful? Give feedback.
All reactions