TECH TO THE POINT

ISSUE:   On Windows command prompt, while running node.js packages, you get this error. <packagename> is not recognized as an internal or external command, operable program or batch file.   This happens even you path settings in Command window and Environment Variables look correct .   FIX:   Recent Windows update in your system messes up the Node configurations. So, before trying to NPM Install <your package> ,    First try 'DOWNLOAD AND REINSTALL NODE.JS' for a quick fix.

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