As for the written test questions I encountered today, please give me some answers. A.js and b.js require each other, will they fall into an infinite loop? Can the results be exported? How to avoid this problem?
This is to examine the cyclic loading of JavaScript modules You can use the module mechanism of es6 to get around this problem. ES6's handling of "cyclic loading" is fundamentally different from CommonJS. ES6 doesn't care at all whether "loop loading" occurs, it just generates a reference to the loaded module. The developer needs to ensure that the value can be obtained when the value is actually obtained.
Then this problem can be understood as a circular reference problem in CommonJS. CommonJS's approach is that once a module is "loop loaded", only the executed part will be output, and the unexecuted part will not be output.
If you understand the circular reference between two modules conceptually, it also involves the module reference of es6.
import b from 'b'
ES6 does not care at all whether "loop loading" occurs, it just generates a reference to the loaded module. The developer needs to ensure that the value can be obtained when the value is actually obtained.
Simply using CommonJs or simply using esm (es6 module) will not cause an infinite loop. But it can happen if you mix the two.
I recommend Ruan Yifeng’s blog, which is very well written. http://www.ruanyifeng.com/blo...
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
This is to examine the cyclic loading of JavaScript modules
You can use the module mechanism of es6 to get around this problem. ES6's handling of "cyclic loading" is fundamentally different from CommonJS. ES6 doesn't care at all whether "loop loading" occurs, it just generates a reference to the loaded module. The developer needs to ensure that the value can be obtained when the value is actually obtained.
If you understand it literally, only use
Then this problem can be understood as a circular reference problem in CommonJS. CommonJS's approach is that once a module is "loop loaded", only the executed part will be output, and the unexecuted part will not be output.
If you understand the circular reference between two modules conceptually, it also involves the module reference of es6.
ES6 does not care at all whether "loop loading" occurs, it just generates a reference to the loaded module. The developer needs to ensure that the value can be obtained when the value is actually obtained.
Simply using CommonJs or simply using esm (es6 module) will not cause an infinite loop. But it can happen if you mix the two.
I recommend Ruan Yifeng’s blog, which is very well written.
http://www.ruanyifeng.com/blo...