TECH TO THE POINT

 ISSUE: Node.js modules build errors NPM install Errors:  '../build/Release/bson' 'MODULE_NOT_FOUND'  js-bson: Failed to load c++ bson extension, node-gyp.js rebuild, ENOENT CAUSE: Even  if python path is set in the Windows' environment variable and in the path, node-gyp is not picking the python path . If you type 'python' from any directory it might work. But node-gyp will still through these errors.  It is confusing as in CLI python works if you call python.exe, but node-gyp doesn't find it, so you decide to try on every thing else you can find online. - If there is a C++ error , node-gyp rely on visual studio's C++ compiler to build. You might need to set Visual C++ path or version in the CLI command.  - long directory or path name issue in Windows: Windows only can handle 260 charecters in a given path name (oooooooooops. This is not an easy fix for windows as the core OS is built on top of this limitation.) . You have to make it sim...

ERROR: npm WARN engine phonegap@2.9.0rc1-0.12.0: wanted: {"node":">=0.10.0"} (current: {"node":"v0.8.20","npm":"1.2.11"})   npm  Error: ENOENT phonegap\node_modules\shelljs\package.json FIX: As you see the warning itself shows version incompatibility. This warning further down will fire few errors with installing 'package.json' and others. Fixing the version of nodejs will fix the most errors. So install new version  for nodejs or update the nodejs with nvm .   npm cache clean - will not work in this case as the Nodejs 0.10.29 doesn't show install steps in the console unless you set it up. ERROR: “‘npm’ is not recognized as an internal or external command, operable program or batch file.”   FIX: --- Restart  the system. Some times the Path doesn't take effect until a restart in windows.