Repository navigation
iojs-v1.0.1-x64.msi uninstalls existing nodejs installation #398
Description
Activity
FYI, you can download the standalone executable (found under the dist/v1.0.1/win-... directories) and put it in your PATH as a workaround (see #361 comments), but I agree that the installer should ideally not be so strong-armed since it's likely the first thing people will use (and there's somewhat of a related problem on OS X in #389).
I'm glad someone reported this separately, since #361 got closed as soon as they resolved the part where it was breaking npm.
I very keen to use
io.jsbut I dont want to loose my currentnodejsinstallation as lot of my projects run on it. I think it would be good to have option to have both co-exist even if you are installingio.jsusing the installer. As a new user I want to tryio.jsbefore I can completely switch to it.@gyandeeps the
nvmproject is working on solving this.I agree this is an issue. It can be resolved by changing the UpgradeCode in the MSI package.
What concerns me is that if we change the code now, an upgrade from iojs 1.0.x to a future version of iojs will fail. What's the best course of action?
@piscisaureus Fail how? If the new installer just won't install, we can simply highlight in the release notes that you need to uninstall the old version first.
Fail how? If the new installer just won't install
In unexpected ways :) The installer isn't made to overwrite existing files.
we can simply highlight in the release notes that you need to uninstall the old version first.
But indeed we can do that (and maybe at a message to the installer as well).
Please test #431
This will be fixed in iojs 1.0.2.
So it to worked on my single test machine today but only after reboot.
The initial effect was for io and node to stop working :(
Is there an option to broadcast the env change in the installer with something like@No9 AFAIK the command prompt does not respond to WM_SETTINGCHANGE messages. A reboot should not be needed, but console windows need to be closed and re-opened.
The general issue (io.js uninstalls node) has been fixed so I'm closing this issue.
Selected a different folder for install to avoid this, but install still removed shortcuts, binaries, and batch files in the program files\nodejs folder.
Attempting to reinstall original nodejs results in installer cancelling install because a newer version is already installed, and does not give option to continue.
Any reason why the windows install can't treat nodejs and iojs as separate programs? Doesn't make sense that I would have to choose between one or the other.