jeena/en.javascript.info
1
0
Fork 0
Code Issues Pull requests Projects Packages Wiki Activity Actions

minor fixes

Browse source
This commit is contained in:
Ilya Kantor 2021-05-24 11:57:17 +03:00
parent fc3c0714db
commit 7a30a00f00
1 changed files with 1 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

2
1-js/13-modules/01-modules-intro/article.md
View file

@ -191,7 +191,7 @@ In other words, a module can provide a generic functionality that needs a setup.
Here's the classical pattern: Here's the classical pattern:
1. A module exports some means of configuration, e.g. a configuration object. 1. A module exports some means of configuration, e.g. a configuration object.
2. On the first import we initialize it, write to its properties. The top-level application script may do that. 2. On the first import we initialize it, write to its properties. The top-level application script may do that.
3. Further imports use the module. 3. Further imports use the module (it's now configured).
For instance, the `admin.js` module may provide certain functionality, but expect the credentials to come into the `config` object from outside: For instance, the `admin.js` module may provide certain functionality, but expect the credentials to come into the `config` object from outside: