Home > Article > Web Front-end > Analysis of JS modularity
This article mainly introduces the analysis of JS modularization, which has certain reference value. Now I share it with everyone. Friends in need can refer to it
Encapsulate a complex program into several files according to certain specifications and combine them together
Reduce complexity, improve decoupling, and facilitate deployment
Avoid naming conflicts (reduce namespace pollution)
Better separation, on-demand loading
Higher reusability
High maintainability
Every file can be As a module
On the server side: the module is loaded synchronously during runtime
On the browser side: the module needs to be compiled and packaged in advance Processing
Module introduction: require(xxx)
Third-party module: xxx is the module name
Custom module: xxx is the module file path
Exposed module: exports.xxx = value and module.exports = value
The essence of the exposed module is the exports object
Exports itself is an empty object exports.xxx = value is to add attributes or methods to the exports object
Module.exports = value is to directly overwrite the original empty object with the new value object
Server-side implementation: Node .js
Browser-side implementation: Browserify (CommonJS browser-side packaging tool)
Download and install browserify
Global: npm install browserify -g
Local: npm install browserify --save-dev
Define module code ( js file code and expose the corresponding content)
Introduce the module Use require to introduce the module in app.js but the browser does not recognize the require method and needs to package and process js
In the terminal in the root directory, enter browserify js/src/app.js -o js/dist/bundle.js (js/src/app.js source file js/dist/bundle.js is the packaged output file )
Page usage introduction:
141d4ec63c56a0a7523a7f892721960e2cacc6d41bbb37262a98f745aa00fbf0 (What the browser actually runs is the file generated by the package)
is specially used Due to the modularization specification on the browser side, module loading is asynchronous
Define exposed modules:
//定义没有依赖的模块: define(function(){ return 模块 }) //定义有依赖的模块: define(['module1','module2'],function(m1,m2){ return 模块 })
Introduce the use module:
require(['module1','module2'],function(m1,m2){ 使用m1/m2 })
Require.js
Define exposed module:
//定义没有依赖的模块: define(function(require,exports,module){ exports.xxx = value module.exports = value }) //定义有依赖的模块: define(function(require,exports,module){ //引入依赖模块(同步) var module2 = require("./module2") //引入依赖模块(异步) require.async("./module3",function(m3){ }) //暴露模块 exports.xxx = value })
Introduce using module:
require(function(require){ var m1 = require('./module1') var m4 = require('./module4') m1.show() m4.show() })
Export module: export xxx
Import module: import xxx from "url"
Page introduction
Use Babel to compile ES6 to ES5 code
Using Browserify to compile and package js
The above is the entire content of this article. I hope it will be helpful to everyone’s learning. For more related content, please pay attention to the PHP Chinese website !
related suggestion:
Parsing of javascript’s immediate execution function
The above is the detailed content of Analysis of JS modularity. For more information, please follow other related articles on the PHP Chinese website!