What is the difference between node environment and browser environment?

Difference: 1. This in node points to global, but in the browser it points to window; 2. Node uses the CommonJS standard, while the browser uses the ES Modules standard; 3. js in the browser can operate the DOM, but node No; 4. I/O read and write operations are different; 5. Module loading is different.

The operating environment of this tutorial: windows7 system, nodejs version 12.19.0, DELL G3 computer.

The difference between node environment and browser environment

1. The point of this in the global environment

In node, this points to global and in the browser This in the middle points to the window, which is why a root is defined in underscore;

var root = typeof self == 'object' && self.self === self && self || typeof global == 'object' && global.global === global && global || this;

And a lot of APIs are encapsulated under the window in the browser, such as alert, document, location, history, etc. There are many. We cannot use xxx(); or window.xxx(); in the node environment. Because these APIs are browser-level encapsulation, they are not available in pure JavaScript. Of course, node also provides many node-specific APIs.

2. Module Standard

Node.js uses the CommonJS module system, and in browsers we are starting to see the ES Modules standard being implemented.

In practice, this means that you temporarily use require() in Node.js and import in the browser.

3. DOM operation

In most cases, js in the browser operates the DOM directly or indirectly (some virtual DOM libraries and frameworks). Because the code in the browser mainly works in the presentation layer. But node is a server-side technology. There is no front page, so we will not operate the DOM in node.

4. I/O reading and writing

Unlike browsers, we need to read and write files like other server-side technologies. Nodejs provides more convenient components. And the browser (to ensure compatibility) has a lot of trouble if it wants to directly open a local image in the page (don't tell me it's not simple, relative path... Just try it and you will know, or find a library Either it is a binary stream, or it is uploaded and the network address is displayed. Otherwise, why would anyone build a js library?), and all of this node is done with one component.

5. Module loading

One characteristic of JavaScript is that the native API that does not provide package references executes all the things to be loaded at once. Here is what we need to see Thank you for your closure skills. All the things used are together, there is no divide and conquer, and there is no logic or reusability. If the page or website is simple, of course we can use some AMD and CMD js libraries (such as requireJS and seaJS) to get it done. In fact, many large websites do this.

The CMD module loading API is provided in nodeJS. If you have used seaJS, you should get started quickly.

Node also provides npm, a package management tool, which can more effectively and conveniently manage our drinking libraries

Of course, ES6 in the browser also has supplements in this regard. I believe it will be better in the future. . . .

For more node-related knowledge, please visit:nodejs tutorial!

The above is the detailed content of What is the difference between node environment and browser environment?. For more information, please follow other related articles on the PHP Chinese website!