NodeJS, NPM installation configuration and test steps (Windows version)

1, Windows Nodejs installation is more convenient (after v0.6.0 version, support Windows native), only need to login official website (http://nodejs.org/), you can see the homepage of the "Install" button, A direct click will automatically download the installation.

2, the installation process is basically directly "NEXT" can be. (The installation MSI file for Windows adds the system variable for path directly in the process, and the variable value is your installation path, such as "C:\Program Files\nodejs"). 3. After the installation is complete, you can use CMD (win+r and then enter CMD to enter) to test whether the installation is successful. Method: Enter node-v under CMD, the version prompt is complete the installation of Nodejs. 4, the installation of NPM. Since NPM has been integrated with the new version of Nodejs, NPM has been installed as well. You can also use the cmd command line to enter "Npm-v" to test for successful installation.  For example, the version prompt will be OK. 5, the construction of conventional nodejs has been completed so far, you can enter "cmd" input "node" into node development mode, enter your Nodejs first sentence: "Hello World"-Input: Console.log (' Hello World '). In addition, you can write a JS file to test the HTTP request, the code is as follows:

var http = require ("http"); Http.createserver (function (request, response) {      Response.writehead (200, {") Content-type ":" Text/plain "});      Response.Write ("Hello World 9999");      Response.End ();}). Listen (9999); Console.log ("Nodejs Start listen 9999 port!");

Save the above code as a test.js file, then switch to the current file directory on the command line, execute node test.js, then open IE, enter http://127.0.0.1:9999 to see the strings we are familiar with.

6, NPM as a Nodejs module management, before I because no system to see the data so that the installation of the configuration module took a large part of the detour, so now it is necessary to list to record.(I have a problem in the configuration process, the ②, ③ steps as follows, the CMD will prompt insufficient permissions, we recommend that you use CMD to do this step, use Administrator privileges to open cmd, and then follow the steps below)①, we will first configure the NPM Global Module storage path and the path of the cache, for example, I would like to put the above two folder in the Nodejs home directory, the Nodejs under the establishment of "Node_global" and "Node_cache" two folders. such as ②, start cmd, enter

NPM config set prefix "C:\Program files\nodejs\node_global"
And
NPM config set cache "C:\Program files\nodejs\node_cache"

③, now let's install a module to try, choose Express this more common module. Also in the cmd command line, enter "NPM Install Express-g" ("-g" This parameter means to be loaded into the global directory, which is said to set the "C:\Program Files\nodejs\node_global" inside. ）。 After the installation process in the CMD is finished scrolling, it will prompt "express" where it is installed, the version and its directory structure. such as ④, close cmd, open the System dialog box, my Computer right-click Properties-Advanced system Settings-advanced-environment variables. As ⑤, enter the Environment Variables dialog box, create a new "Node_path" under System variables, and enter "C:\Program files\nodejs\node_global\node_modules". (PS: This step is quite critical.) 2014.4.19 added: Because the module's default address is changed, the above user variables are changed (the user variable "PATH" is modified to "C:\Program files\nodejs\node_global\"), Not using the module causes the input command to appear "XXX is not an internal or external command, it is not a running program or batch file" error.

⑥, the above steps are OK, we can open the cmd command line again, enter node, enter "require (' Express ')" To test the next node's module global path is configured correctly. The correct CMD will list information about the Express. such as (if the error is generally node_path configuration is wrong, you can check the next step ④⑤)

NodeJS, NPM installation configuration and test steps (Windows version)