Previous review

In the last article we talked about CommonJs. If you haven’t read it yet, you can find the column where this article is located to learn.
CommonJs has many excellent features, let’s briefly review them below:

Module code only runs after loading;
The module can only be loaded once;
The module can request to load other modules;
Supported Circular dependencies;
Modules can define public interfaces, and other modules can observe and interact based on this public interface;

天下狠CommonJs 久矣

Es Module is unique in that it can be loaded natively through the browser or with third-party loaders and build tools.
Browsers that support Es module modules can load the entire dependency graph from the top-level module, and it is done asynchronously. The browser will parse the entry module, determine the dependencies, and send a request for the dependent module. After these files are returned over the network, the browser will resolve their dependencies, and if these secondary dependencies have not been loaded, more requests will be sent.
This asynchronous recursive loading process will continue until the entire application's dependency graph has been resolved. After the dependency graph is parsed, the reference program can officially load the module.
Es Module not only borrows many excellent features of CommonJs and AMD, but also adds some new behaviors:

Es Module is executed in strict mode by default;
Es Module does not share the global namespace;
Es Module The value of the top-level this is undefined (regular script is window );
The var declaration in the module will not be added to the window object;
##Es Module is loaded and executed asynchronously;

export and import

exports and import. The
export command is used to specify the external interface of the module, and the import command is used to import the functions provided by other modules.

Basic use of export

export const nickname = "moment";
export const address = "广州";
export const age = 18;

Copy after login

const nickname = "moment";
const address = "广州";
const age = 18;

export { nickname, address, age };

Copy after login

export function foo(x, y) {
  return x + y;
}

export const obj = {
  nickname: "moment",
  address: "广州",
  age: 18,
};

// 也可以写成这样的方式
function foo(x, y) {
  return x + y;
}

const obj = {
  nickname: "moment",
  address: "广州",
  age: 18,
};

export { foo, obj };

Copy after login

export is the original name, but can be renamed using the as keyword.

const address = "广州";
const age = 18;

export { nickname as name, address as where, age as old };

Copy after login

export default "foo";

export default { name: 'moment' }

export default function foo(x,y) {
  return x+y
}

export { bar, foo as default };

Copy after login

Incorrect use of export

if(true){
export {...};
}

Copy after login

export Must provide an external interface:

// 1只是一个值,不是一个接口export 1// moment只是一个值为1的变量const moment = 1export moment// function和class的输出，也必须遵守这样的写法function foo(x, y) {    return x+y
}export foo复制代码

Copy after login

Basic use of import

export command to define the external interface of the module, other js files can be loaded through the import command The entire module

import {foo,age,nickname} from '模块标识符'

Copy after login

import The command accepts a curly bracket, which specifies the variable name to be imported from other modules, and the variable name must be the same as the name of the external interface of the imported module.

Completely understand es6 modularization in one article

从上图可以看得出来,对象的属性被重新赋值了,而变量的则报了 Assignment to constant variable 的类型错误。
如果模块同时导出了命名导出和默认导出,则可以在 import 语句中同时取得它们。可以依次列出特定的标识符来取得,也可以使用 * 来取得:

// foo.js
export default function foo(x, y) {
  return x + y;
}

export const bar = 777;

export const baz = "moment";

// main.js
import { default as foo, bar, baz } from "./foo.js";

import foo, { bar, baz } from "./foo.js";

import foo, * as FOO from "./foo.js";

Copy after login

动态 import

标准用法的 import 导入的模块是静态的，会使所有被导入的模块，在加载时就被编译（无法做到按需编译，降低首页加载速度）。有些场景中，你可能希望根据条件导入模块或者按需导入模块，这时你可以使用动态导入代替静态导入。
关键字 import 可以像调用函数一样来动态的导入模块。以这种方式调用，将返回一个 promise。

import("./foo.js").then((module) => {  const { default: foo, bar, baz } = module;  console.log(foo); // [Function: foo]
  console.log(bar); // 777
  console.log(baz); // moment});复制代码

Copy after login

使用顶层 await

在经典脚本中使用 await 必须在带有 async 的异步函数中使用,否则会报错:

import("./foo.js").then((module) => {
  const { default: foo, bar, baz } = module;
  console.log(foo); // [Function: foo]
  console.log(bar); // 777
  console.log(baz); // moment
});

Copy after login

而在模块中,你可以直接使用 Top-level await:

const p = new Promise((resolve, reject) => {  resolve(777);
});const result = await p;console.log(result); 
// 777正常输出

Copy after login

import 的错误使用

由于import是静态执行，所以不能使用表达式和变量，这些只有在运行时才能得到结果的语法结构。

// 错误
import { 'b' + 'ar' } from './foo.js';

// 错误
let module = './foo.js';
import { bar } from module;

// 错误
if (x === 1) {
  import { bar } from './foo.js';
} else {
  import { foo } from './foo.js';
}

Copy after login

在浏览器中使用 Es Module

在浏览器上,你可以通过将 type 属性设置为 module 用来告知浏览器将 script 标签视为模块。

<script></script><script></script>

Copy after login

模块默认情况下是延迟的,因此你还可以使用 defer 的方式延迟你的 nomodule 脚本:

  <script>      
  console.log("模块情况下的");
    </script>    
    <script></script>
    <script>
      console.log("正常 script标签");    
      </script>

Copy after login

Completely understand es6 modularization in one article

在浏览器中,引入相同的 nomodule 脚本会被执行多次,而模块只会被执行一次:

    <script></script>    <script></script>

    <script></script>
    <script></script>
    <script></script>

Copy after login

Completely understand es6 modularization in one article

模块的默认延迟

默认情况下,nomodule 脚本会阻塞 HTML 解析。你可以通过添加 defer 属性来解决此问题,该属性是等到 HTML 解析完成之后才执行。

Completely understand es6 modularization in one article

defer and async are optional attributes, they can only choose one of them, under the nomodule script, defer The current script will not be parsed until HTML is parsed, and async will be parsed in parallel with HTML and will not block the parsing of HTML , the module script can specify the async attribute, but it is invalid for defer, because the module is delayed by default.
For module scripts, if the async attribute is present, the module script and all its dependencies will be parsed and fetched in parallel, and the module script will be executed as soon as it is available.

The difference between Es Module and Commonjs

Before discussing the Es Module module, you must first understand the Es Module and Commonjs are completely different, they have three completely different types:

CommonJS The module outputs a copy of the value, Es Module The output is a reference to the value;
CommonJS module is loaded at runtime, and Es Module is the compile-time output interface.
CommonJS The require() of the module is to load the module synchronously, and the import command of the ES6 module is to load asynchronously and has an independent module dependency analysis stage.

The second difference is because CommonJS loads an object (that is, the module.exports property), which is only available when the script is running It will be generated after completion. And Es Module is not an object. Its external interface is just a static definition, which will be generated during the static analysis phase of the code.
Commonjs What is output is a copy of the value. That is to say, once a value is output, changes within the module will not affect the value. For details, please see the previous article. The operating mechanism of
Es Module is different from CommonJS. JS Engine When statically analyzing a script, a read-only reference will be generated when the module loading command import is encountered. When the script is actually executed, the value will be retrieved from the loaded module based on this read-only reference. In other words, import is a connection pipe. If the original value changes, the value loaded by import will also change accordingly. Therefore, Es Module is a dynamic reference and does not cache values. The variables in the module are bound to the module in which they are located.

Related concepts of the working principle of Es Module

Before learning the working principle, we might as well understand the related concepts.

Module Record

Module Record (Module Record) encapsulates structural information about the import and export of a single module (the current module). This information is used to link the import and export of the connected module set. A module record consists of four fields, which are only used when executing the module. The four fields are:

Realm: Create the scope of the current module;
Environment: Module The top-level binding environment record of Runtime property-based access. Module namespace objects have no constructor;
HostDefined: field is reserved for use by
, additional information is required to associate with the module. Module Environment Record

A module environment record is a declarative environment record used to represent the external scope of an ECMAScript module. In addition to the ordinary mutable and immutable bindings, module environment records also provide immutable

import

bindings that provide binding to a target that exists in another environment record indirect access.

Immutable binding means that the current module introduces other modules, and the introduced variables cannot be modified. This is the unique immutable binding of the module.

Es Module parsing process

Before we start, let’s have a rough idea of what the entire process is like. Let’s have a general understanding:

Phase 1: Construction (Construction), find the js file according to the address, download it through the network, and parse the module file to Module Record;
Phase 2: Instantiation (Instantiation), instantiate the module, allocate memory space, parse the import and export statements of the module, and point the module to the corresponding memory address;
Phase 3: Run (Evaluation), run the code, calculate the value, and fill the value into the memory address;

Construction construction phase

loader is responsible for addressing and downloading modules. First we modify an entry file, which in HTML is usually a <script type="module"></script> tag to represent a module file.

Completely understand es6 modularization in one article

The module continues to be declared through the import statement. There is a module declaration identifier in the import declaration statement. Character (ModuleSpecifier), which tells loader how to find the address of the next module.

Completely understand es6 modularization in one article

Each module identification number corresponds to a module record (Module Record), and each module record Contains JavaScript code, execution context, ImportEntries, LocalExportEntries, IndirectExportEntries, StarExportEntries . The ImportEntries value is a ImportEntry Records type, and LocalExportEntries, IndirectExportEntries, StarExportEntries is a ExportEntry Records type.

ImportEntry Records

A ImportEntry Records contains three fields ModuleRequest, ImportName,LocalName;

ModuleRequest: a module identifier (ModuleSpecifier);
ImportName: generated by ModuleRequest The name of the required binding for the module export of the module identifier. The value namespace-object indicates that the import request is for the namespace object of the target module;
LocalName: variable used to access the imported value from the current module from the imported module;

For details, please refer to the figure below:
The following table records the ImportEntry Records fields imported using import Example:

##import React from "react";"react""default""React"import * as Moment from "react";"react"namespace -obj"Moment"import {useEffect} from "react";"react""useEffect" "useEffect"##import {useEffect as effect } from "react";

ExportEntry Records

A ExportEntry Records contains four fields ExportName, ModuleRequest, ImportName , LocalName, and ImportEntry Records are different in that there is an additional ExportName.

ExportName: The name this module uses to bind when exporting.

The following table records examples of ExportEntry Records fields exported using export:

Import Statement From	Module identifier(ModuleRequest)	Import name(ImportName)



"react"	"useEffect"	"effect"

##export {x};"x"nullnull "x"##export {v as x};##export {x} from "mod";"x""mod""x"nullexport {v as x} from "mod";"x""mod""v"nullnull##export * as ns from "mod";"ns"mod"allnull

Back to topic

Only after parsing the current Module Record can we know which submodules the current module depends on , then you need to resolve the submodule, obtain the submodule, then parse the submodule, and continuously cycle this process resolving -> fetching -> parsing. The result is as shown in the figure below:

Completely understand es6 modularization in one article

This process is also called static analysis. It will not run JavaScript code and will only identify export and import keyword, so import cannot be used in non-global scope, except for dynamic import.
What if multiple files depend on one file at the same time? Will this cause an infinite loop? The answer is no.
loader Use Module Map to track and cache the global MOdule Record to ensure that the module is only fetch Once, there will be an independent Module Map in each global scope.

MOdule Map is a key/value mapping object composed of a URL record and a string. The URL record is the request URL to get the module, a string indicating the type of module (e.g. "javascript"). The value of the module map is either the module script, null (used to indicate a failed fetch), or the placeholder value "fetching".

Completely understand es6 modularization in one article

linking linking phase

After all Module Record are parsed, the next JS engine needs Link all modules. The JS engine takes the Module Record of the entry file as the starting point, recursively links the modules in depth-first order, and creates a Module Environment Record for each Module Record. Used to manage variables in Module Record.

Completely understand es6 modularization in one article

##Module Environment Record has a Binding, which is used to store Module The variables exported by Record, as shown in the figure above, export a variable of count at the module main.js, in Module Environment Record The Binding will have a count. At this time, it is equivalent to the compilation phase of V8, creating a module instance object, adding the corresponding attributes and Method, the value at this time is undefined or null, allocate memory space for it.
import keyword is used in the submodule count.js to import main.js, and count. The import of js and the export variable of main.js point to the same memory location, thus linking the relationship between the parent and child modules. Woke up. As shown below:

Completely understand es6 modularization in one article

需要注意的是,我们称 export 导出的为父模块,import 引入的为子模块,父模块可以对变量进行修改,具有读写权限,而子模块只有读权限。

Evaluation 求值阶段

在模块彼此链接完之后,执行对应模块文件中顶层作用域的代码，确定链接阶段中定义变量的值，放入内存中。

Es module 是如何解决循环引用的

在 Es Module 中有5种状态，分别为 unlinked、linking、linked、evaluating和 evaluated，用循环模块记录(Cyclic Module Records)的 Status 字段来表示,正是通过这个字段来判断模块是否被执行过,每个模块只执行一次。这也是为什么会使用 Module Map 来进行全局缓存 Module Record 的原因了,如果一个模块的状态为 evaluated,那么下次执行则会自动跳过,从而包装一个模块只会执行一次。 Es Module 采用 深度优先 的方法对模块图进行遍历,每个模块只执行一次,这也就避免了死循环的情况了。

深度优先搜索算法（英语：Depth-First-Search，DFS）是一种用于遍历或搜索树或图的算法。这个算法会尽可能深地搜索树的分支。当节点v的所在边都己被探寻过，搜索将回溯到发现节点v的那条边的起始节点。这一过程一直进行到已发现从源节点可达的所有节点为止。如果还存在未被发现的节点，则选择其中一个作为源节点并重复以上过程，整个进程反复进行直到所有节点都被访问为止。

Completely understand es6 modularization in one article

看下面的例子,所有的模块只会运行一次:

// main.js
import { bar } from "./bar.js";
export const main = "main";
console.log("main");

// foo.js
import { main } from "./main.js";
export const foo = "foo";
console.log("foo");

// bar.js
import { foo } from "./foo.js";
export const bar = "bar";
console.log("bar");

Copy after login

通过 node 运行 main.js ,得出以下结果:

Completely understand es6 modularization in one article

好了,这篇文章到这也就结束了。《JavaScript视频教程》

Export declaration	Export name	Module identifier	Import name	Local name
export var v;	"v"	null	null	"v"
export default function f() {}	"default"	null	null	"f"
export default function () {}	"default"	null	null	"default"
export default 42;	"default"	null	null	"default"

"x"	null	null	"v"

				##export * from "mod";
"mod"	all-but-default	null

The above is the detailed content of Completely understand es6 modularization in one article. For more information, please follow other related articles on the PHP Chinese website!