I currently have node.js v0.10.24-x64 installed on my machine and am attempting to update to v12.19.0-x64. When I run the v12.19.0-x64.msi installer, I see this error message: https://i.stack.imgur.com/J1mAK.png
Clicking 'cancel' then gives this message, indicating that the installer is trying to remove a prior installation of node: https://i.stack.imgur.com/6Vcme.png
I've tried uninstalling my current node.js installation and then installing the newer version from scratch, but this process gives me the same result. How can I completely remove node.js from my system so that I can install the new version without errors?
Try installing or uninstalling node js without connecting you pc to internet.
I'm trying to install Node JS v8.12.0 on Windows 7, using the following installer downloaded from the Node website: https://nodejs.org/dist/v8.12.0/node-v8.12.0-win-x86.zip
When I run the installer, it just hangs on the first window it opens - please see screen below.
It may have something to do with the fact that I uninstalled a previous version of Node by following this solution: How to completely remove node.js from Windows
I also had NVM for Windows installed previously, which I also uninstalled.
So I am trying to install Node again from scratch, but this time it just hangs forever.
I'm running it with Elevated Privileges on a work machine, which has always worked when installed Node in the past, including this version (8.12.0).
I guess you are using the binary version of Node for Windows.
Try to download and use this installer:
https://nodejs.org/dist/latest-v8.x/node-v8.15.0-x86.msi
I use a Windows 10 x64 Pro machine as a development environment.
Today I went to the Node.js site, (nodejs.org/en/download) to get the LTS version which is 8.11.4 for Node and includes npm 5.6.0. This information is visible at the top of the page.
After installation, I did the command "node -v" and actually this gives me v8.11.4 as result. On the other hand the same command for npm "npm -v" gives me version 2.15.10.
What troubles me is that different documentation suggests that the update is done by installing the latest version, which I did, with the result that I have; the wrong NPM version.
I need at least NPM version 3.x or higher. As a lead already explored without success;
- clean installation from the original site by choosing the LTS version, branch x64
- uninstalled the version and reinstalled
Is it a known bug or is there another avenue to explore?
The short version is: VS 2017 installs a really old version of NPM.
By doing the following command in powershell "npm config get prefix" I could see that the prefix was pointing to Microsoft. Then I used the "npm-windows-upgrade" tool to get the installer path for VS. From there I navigated to the bin folder and launched the JavaScript file to start the update.
VS2017 looks to use version 2.15.10.
The path to it is c:users{userprofile}.mpmrc
I just deleted this file and all ran fine (i'm not using VS).
The Web platform installer only installs the latest version.
I have also tried using offline installer, but it seems there is an existing issue with 5.3.301 runtime fresh install on Windows10 anniversary version. Please help. I'm stuck here very bad. Any other possible ways to install?
I am trying to install socket.io on windows with npm for use on a nodeJS server.
First, when I typed "npm install socket.IO" i had an error in the log saying something about python and node-gyp. I installed python 2.7.3 and set the environment variables.
Now I got a new error, which has something to do with visual studio (what the hell does VS have to do with npm ? Is it about the compiler? ).
The error is the same as here npm install for some packages (sqlite3, socket.io) fail with error MSB8020 on Windows 7
But when I use the option in the answer instead of the error it tells me something about a possible data loss (c4267) but doesn't log any error.
Then when I start my app, it tells me cannot find module socket.io still
What could this come from ?
Oh and also when i do npm config get root it tells me "undefined" could it have anything to do with it ?
Should I install the modules globally or locally ?
At least one of the packages in Socket.IO's dependency tree is a C/C++ addons which needs to be compiled on your system as it's installed. And, since it's a dependency, if it doesn't succeed in installing, neither will Socket.IO.
To enable cross-system compilation, Node.js uses node-gyp as its build system. You'll need to have it installed as a global package:
npm install -g node-gyp
As well as have its dependencies installed. Abridged version:
Python 2
C/C++ Compiler / Build Tools
For Windows, Microsoft Visual Studio 2013 (C++ or Windows Desktop) (Express edition)
For 64-bit, may need Windows 7 64-bit SDK
Then, you should be able to install Socket.IO as a local package so you can require it:
npm install socket.io
I had a similar problem on Mac.
What resolved my problem is installing a slightly older version of Socket.io.
I did:
npm install socket.io#"~0.8.1"
which would install the latest version between 0.8.0 to 0.8.9, but not 0.9.0 or above.
Socket.io then installed perfectly.
Make sure you have all the required software to run node-gyp:
https://github.com/TooTallNate/node-gyp
You can configure version of Visual Studio used by gyp via an environment variable so you can avoid having to set the --msvs_version=2012 property.
Examples:
set GYP_MSVS_VERSION=2012 for Visual Studio 2012
set GYP_MSVS_VERSION=2013e (the 'e' stands for 'express edition')
For the full list see
- https://github.com/joyent/node/blob/v0.10.29/tools/gyp/pylib/gyp/MSVSVersion.py#L209-294
This is still painful for Windows users of NodeJS as it assumes you have a copy of Visual Studio installed and many end users will never have this. So I'm lobbying Joyent to the encourage them to include web sockets as part of CORE node and also to possible ship a GNU gcc compiler as part of NodeJS install so we can permanently fix this problem.
Feel free to add your vote at:
https://github.com/joyent/node/issues/8005#issuecomment-50545326
The problem causing the compile failure is that the ws module installed by the engine.io module required by socket.io pulls in a backlevel version of nan. See https://github.com/BrowserSync/grunt-browser-sync/issues/95 for details. To work around the problem after the build failure:
cd to node_modules/socket.io/node_modules/engine.io/node_modules/ws
edit package.json to change the release of nan from 1.4.x to 1.6.0
issue command node-gyp rebuild
You should now be able to use socket.io
Another approach is to use Docker for Windows and spin up a NodeJS environment. While developing you can mount your Node code as a Docker volume and so continue to update your code from Windows but execute it and install it's dependencies inside a Linux VM. When you deploy you might prefer to use a Dockerfile that COPY's your Node code into your Docker image and so bakes it into the release image you deploy.
This approach might be required if you don't want to risk changing the socket.io version of your code or its dependencies.
It also may be a valuable solution if you planned to deploy to a corporate Intranet or public/private Cloud.
Docker can also be very handy for testing deployment under different versions of Node without disturbing the development environment of your Windows computer (e.g. for testing a NodeJS lib).
Official NodeJS Docker images
An explanation of how to use these images
this problem makes me very troubled..
I tried many solutions.
I installed .NET Framework 2.0 SDK.
I installed Python 2.7.x
I installed VS 2012 Express
I set some paths
I executed npm install xxx with the argument --msvs_version=2010(or 2012/2013..)...
But all failed.
finally, I uninstalled Python & .NET Framework 2.0 SDK & VS 2012, clear those paths,enable Windows Update, install all essential updates, restart my computer
then execute commands below:
npm install node-gyp -g
npm install socket.io -g
npm install browser-sync -g
there is no errors in installation logs.
Note : this solution may not work for you, but for me