Notes for Windows Users
After Downloading the SDK, you also need to install:
- Python (v2.7.3+ recommended, v3.x.x is not supported)
Make sure that you have a PYTHON environment variable, and it is set to C:\path\to\python.exe, not to a folder
- npm (v3.x.x+)
Make sure npm version is at least 3. Otherwise you may get an error of “path name too long” or so when npm install in a project folder.
To check the version of npm, use:
npm -v
To upgrade npm to the latest version, use:
npm install npm -g
ERR! code ELIFECYCLE.If you see the following error when running npm install in a project folder:
npm ERR! code ELIFECYCLE
npm ERR! spawn-sync@1.0.13 postinstall: node postinstall
npm ERR! Exit status -4058
Try deleting the existing node_modules folder and running:
npm install --ignore-scripts
In general, if you encounter any ENOENT error when running npm install in a project folder, it is probably due to npm trying to rewrite a file which is read-only. You can uncheck the read-only option (right-click -> properties -> general) the file raising the permissions error.
Then, delete the node_modules folder in the project and run npm install again.
ERR! code ENOENT.In general, if you encounter any ENOENT error when running npm install in a project folder, it is probably due to npm trying to rewrite a file which is read-only. You can uncheck the read-only option (right-click -> properties -> general) the file raising the permissions error.
Then, delete the node_modules folder in the project and run npm install again.
For Windows XP/Vista/7:
- Microsoft Visual Studio C++ 2013 (Express version works well)
If the install fails, try uninstalling any C++ 2010 x64&x86 Redistributable that you have installed first
If you get errors that the 64-bit compilers are not installed, you may also need the compiler update for the Windows SDK 7.1, available through Microsoft.
For Windows 7/8:
Microsoft Visual Studio C++ 2013 for Windows Desktop (Express version works well)
For 64bit Windows
To use 64-bit builds of Node.js and native modules, you will also need the Windows 7 64-bit SDK
You may need to run one of the following commands if your build complains about WindowsSDKDir not being set, and you are sure you have already installed the SDK:
call "C:\Program Files\Microsoft SDKs\Windows\v7.1\bin\Setenv.cmd" /Release /x64
Or for x86 builds:
call "C:\Program Files\Microsoft SDKs\Windows\v7.1\bin\Setenv.cmd" /Release /x86