官术网_书友最值得收藏!

Modules

Modules provide a way to encapsulate your code and create privacy. In object-oriented languages, we usually use classes for this. However, I actually believe that this is an anti-pattern rather than a good practice. Classes should be used where inheritance is desired and not just to structure your code.

I'm sure that you've encountered a lot of different module patterns in JavaScript already. One of the most popular ones that creates privacy using a function closure of an immediately invoked function expression (IIFE) is probably the revealing module pattern. If you'd like to read more about this and maybe other great patterns, I recommend the book Learning JavaScript Design Patterns, by Addy Osmani.

Within ECMAScript 6, we can now use modules to serve this purpose. We simply create one file per module, and then we use the import and export keywords to connect our modules together.

Within the ECMAScript 6 module specification, we can actually export as many things as we like from each module. We can then import these named exports from any other module. We can have one default export per module, which is especially easy to import. Default exports don't need to be named, and we don't need to know their name when importing them:

import SomeModule from './some-module.js'; 
var something = SomeModule.doSomething();
export default something;

There are many combinations on how to use modules. We will discover some of these together while working on our task management application during the upcoming chapters. If you'd like to see more examples on how to use modules, I can recommend the Mozilla Developer Network documentation (https://developer.mozilla.org) on the import and export keywords.

主站蜘蛛池模板: 文成县| 申扎县| 营口市| 朝阳市| 尖扎县| 社旗县| 长治县| 合阳县| 罗源县| 屏东县| 广安市| 张北县| 遂宁市| 霍山县| 双牌县| 沿河| 永城市| 邵阳县| 民勤县| 依兰县| 潢川县| 水城县| 长汀县| 成安县| 梁山县| 顺昌县| 德化县| 彭泽县| 青岛市| 应城市| 武定县| 樟树市| 军事| 仁布县| 民丰县| 宣化县| 新龙县| 聊城市| 土默特左旗| 昔阳县| 龙州县|