window下nodejs环境怎么配置

JavaScript018

window下nodejs环境怎么配置,第1张

下载node.msi安装文件包,里面包含了node.js和npm;双击node.msi,选择安装路径和npm;

在node的安装的根目录,也就是nodejs文件夹下新建两个名字为node_cache、node_global文件夹

设置环境变量:变量名:NODE_PATH值:D:\Program Files\nodejs\node_global\node_modules。注意:本教程nodejs安装在D:\Program Files\目录下,所以环境变量就这样设置的;

找个项目文件夹,再里面新建一个service文件夹

注意:此路径不能有中文。再在里面新建一个UTF-8编码的js文件

在js文件里面增加入下代码

启动nodejs服务,window键+R,输入cmd然后回车

在黑窗口中输入node G:\nodejs\service\test.js

注意:结尾不用加分号;

回车看结果;

成功:

失败:

node里的js,和前端用的js不一样。。。。前端用的JS,俗称JAVASCRIPT1.0,正规名称是ECMAscript3,而node上用的JS,是ECMAscript6。。

尽管都叫ECMAscript,但相比之下,6和3几乎可以看成两门不同的语言。。3的语法在6中都有,但大概只有6语法总量的三分之一左右。。。另外三分之二,在3中是没有的。。3是基于对象的,而6是面向对象的。。比如6中有类,有lambda表达式,还有静态。。通过学习3,是根本不会涉及这些概念的。。

如果以3作为标准JS的话,那么6只有三分像JS,而七分像C#。。对于前端来讲,限于基础不足,NODE会显得非常难学。。。如果之前没学过C#或者JAVA,其实很难平滑过渡到NODE。。。比如下面这是一个类,你会觉得它是你所认为的JS代码?

class BaseResult{

constructor(code,msg,data){

this.code = code

this.msg = msg

***.data = data

}

setCode(code){

this.code = code

}

getCode(){

return this.code

}

setMsg(msg){

this.msg = msg

}

getMsg(){

return this.msg

}

setData(data){

***.data = data

}

getData(){

return ***.data

}

getRes(){

return {'code':this.code,'msg':this.msg,'data':***.data}

}

}

const SUCCESS = new BaseResult(0,'成功',{a:10,b:[{c:10,d:20},{e:30,f:40}]})

console.log(SUCCESS)

所以如果你目前只是学习前端,NODE可以暂时跳过,因为你根本学不会,即便自己觉得会了,到了做项目,你就明白自己根本不是真会,不理解面向对象,根本做不了完整的后端项目。。。要想转到后端,面向对象的ES6是根本跳不过去的

如果将来有机会学学C#或者JAVA,养成了面向对象思想,再学NODE就会变得非常平滑。。

Introduction

Node.js is a Javascript platform for server-side programming. It

allows users to easily create networked applications that require

backend functionality. By using Javascript as both the client and server

language, development can be fast and consistent.

In this guide, we will show you a few different ways of getting

Node.js installed on a CentOS 7 server so that you can get started. Most

users will want to use the EPEL installation instructions or the NVM

installation steps.

Install Node from Source

One way of acquiring Node.js is to obtain the source code and compile it yourself.

To do so, you should grab the source code from the project’s website.

On the downloads page, right click on the “Source Code” link and click

“Copy link address” or whatever similar option your browser gives you.

On your server, use wget and paste the link that you copied in order to download the archive file:

wget http://nodejs.org/dist/v0.10.30/node-v0.10.30.tar.gz

Extract the archive and move into the new directory by typing:

tar xzvf node-v* &&cd node-v*

There are a few packages that we need to download from the CentOS

repositories in order to compile the code. Use yum to get these now:

sudo yum install gcc gcc-c++

Now, we can configure and compile the software:

./configure

make

The compilation will take quite awhile. When it is finished, you can install the software onto your system by typing:

sudo make install

To check that the installation was successful, you can ask Node to display its version number:

node –version

v0.10.30

If you see the version number, then the installation was completed successfully.

Install a Package from the Node Site

Another option for installing Node.js on your server is to simply get

the pre-built packages from the Node.js website and install them.

You can find the Linux binary packages here. Since CentOS 7 only

comes in the 64-bit architecture, right click on the link under “Linux

Binaries (.tar.gz)” labeled “64-bit”. Select “Copy link address” or

whatever similar option your browser provides.

On your server, change to your home directory and use the wget

utility to download the files. Paste the URL you just copied as the

argument for the command:

cd ~

wget http://nodejs.org/dist/v0.10.30/node-v0.10.30-linux-x64.tar.gz

Note: Your version number in the URL is likely to be different than

the one above. Use the address you copied from the Node.js site rather

than the specific URL provided in this guide.

Next, we will extract the binary package into our system’s local

package hierarchy with the tar command. The archive is packaged within a

versioned directory, which we can get rid of by passing the

–strip-components 1 option. We will specify the target directory of our

command with the -C command:

sudo tar –strip-components 1 -xzvf node-v* -C /usr/local

This will install all of the components within the /usr/local branch of your system.

You can verify that the installation was successful by asking Node for its version number:

node –version

v0.10.30

The installation was successful and you can now begin using Node.js on your CentOS 7 server.

Install Node from the EPEL Repository

An alternative installation method uses the EPEL (Extra Packages for

Enterprise Linux) repository that is available for CentOS and related

distributions.

To gain access to the EPEL repo, you must modify the repo-list of

your installation. Fortunately, we can reconfigure access to this

repository by installing a package available in our current repos called

epel-release.

sudo yum install epel-release

Now that you have access to the EPEL repository, you can install Node.js using your regular yum commands:

sudo yum install nodejs

Once again, you can check that the installation was successful by asking Node to return its version number:

node –version

v0.10.30

Many people will also want access to npm to manage their Node packages. You can also get this from EPEL by typing:

sudo yum install npm

Install Node Using the Node Version Manager

Another way of installing Node.js that is particularly flexible is

through NVM, the Node version manager. This piece of software allows you

to install and maintain many different independent versions of Node.js,

and their associated Node packages, at the same time.

To install NVM on your CentOS 7 machine, visit the project’s GitHub

page. Copy the curl or wget command from the README file that displays

on the main page. This will point you towards the most recent version of

the installation script.

Before piping the command through to bash, it is always a good idea

to audit the script to make sure it isn’t doing anything you don’t agree

with. You can do that by removing the | bash segment at the end of the

curl command:

curl https//raw.githubusercontent.com/creationix/nvm/v0.13.1/install.sh

Take a look and make sure you are comfortable with the changes it is

making. When you are satisfied, run the command again with | bash

appended at the end. The URL you use will change depending on the latest

version of NVM, but as of right now, the script can be downloaded and

executed by typing:

curl https://raw.githubusercontent.com/creationix/nvm/v0.13.1/install.sh | bash

This will install the nvm script to your user account. To use it, you must first source your .bash_profile:

source ~/.bash_profile

Now, you can ask NVM which versions of Node it knows about:

nvm list-remote

. . .

v0.10.29

v0.10.30

v0.11.0

v0.11.1

v0.11.2

v0.11.3

v0.11.4

v0.11.5

v0.11.6

v0.11.7

v0.11.8

v0.11.9

v0.11.10

v0.11.11

v0.11.12

v0.11.13

You can install a version of Node by typing any of the releases you see. For instance, to get version 0.10.30, you can type:

nvm install v0.10.30

You can see the different versions you have installed by typing:

nvm list

-> v0.10.30

system

You can switch between them by typing:

nvm use v0.10.30

Now using node v0.10.30

To set this version as the default, type:

nvm alias default v0.10.30

default ->v0.10.30

You can verify that the install was successful using the same technique from the other sections, by typing:

node –version

v0.10.30

From the version number output, we can tell that Node is installed on our machine as we expected.

Conclusion

As you can see, there are quite a few different ways of getting

Node.js up and running on your CentOS 7 server. If one of the

installation methods is giving you problems, try one of the other

options.