We officially support the LTS (v4.x.x) and Current (v6.x.x) versions of Node.js.
Also, make sure NPM is at least version 3+.
npm install npm -g
Note: We've seen the previous command fail on Windows, if so, delete this file and retry:
Before we jump into installing the bean-sdk, we must first ensure your system is ready to build native Node.js modules using node-gyp.
There are two options for doing this. The option you pick depends on if you have you have Visual Studio installed on your computer. Even for those of you with VS installed, we recommend trying option 1 first! If it doesn't work, move on to option 2.
For those of you who do not have visual studio, install
windows-build-tools using NPM from an elevated PowerShell or CMD.exe (run as Administrator).
npm install --global --production windows-build-tools
If option 1 didn't work for you, and you have Visual Studio installed on your computer, you don't need to install the package from option 1. You simply need to tell
npm which version of Visual Studio you have installed. For example, if it's version 2015, run:
npm config set msvs_version 2015 --global
Note: In addition to having MS Visual Studio installed, you must ensure that C++ toolchain is actually installed. To do this, create a C++ project in VS. By creating a C++ project, additional required dependencies will be installed.
npm install -g bean-sdk
Important: We are currently working through some installation issues in certain Windows environments, particularly those with a pre-existing Visual Studio installation. Please contact us at firstname.lastname@example.org and we will work through any installation issues.
Let's scan for Beans to ensure everything is working properly!
From the terminal:
Try upgrading to the latest possible
npm -g install npm@next
Make sure Python27 is on System Path. When you type
python --version it should report v2.x.x. If this is not the case, configure NPM to use Python2.7...here is an example:
npm config set python C:\Python27\python.exe --global
Uninstall Visual Studio and re-try option 1. It should never come to this, but if it does, this may help.