Reputation: 375

NPM - Can't install socket.IO

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 ?

Upvotes: 18

Answers (6)

hidmouth

Reputation: 1

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

Upvotes: 0

Tony O'Hagan

Reputation: 22692

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).

Upvotes: 0

Jonathan Lonowski

Reputation: 123453

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

Upvotes: 35

David Tootill

Reputation: 571

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

Upvotes: 0

Tony O'Hagan

Reputation: 22692

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: