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

docs: minor grammar fix and link update

Browse source
This commit is contained in:
Huyen Nguyen 2022-02-07 11:08:41 +07:00
parent 71da17e596
commit 5315ba590c
1 changed files with 2 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

4
1-js/13-modules/02-import-export/article.md
View file

@ -93,7 +93,7 @@ At first sight, "import everything" seems such a cool thing, short to write, why
Well, there are few reasons. Well, there are few reasons.
1. Modern build tools ([webpack](http://webpack.github.io) and others) bundle modules together and optimize them to speedup loading and remove unused stuff. 1. Modern build tools ([webpack](https://webpack.js.org/) and others) bundle modules together and optimize them to speedup loading and remove unused stuff.
Let's say, we added a 3rd-party library `say.js` to our project with many functions: Let's say, we added a 3rd-party library `say.js` to our project with many functions:
```js ```js
@ -403,7 +403,7 @@ We can come across two problems with it:
2. `export * from './user.js'` re-exports only named exports, but ignores the default one. 2. `export * from './user.js'` re-exports only named exports, but ignores the default one.
If we'd like to re-export both named and the default export, then two statements are needed: If we'd like to re-export both named and default exports, then two statements are needed:
```js ```js
export * from './user.js'; // to re-export named exports export * from './user.js'; // to re-export named exports
export {default} from './user.js'; // to re-export the default export export {default} from './user.js'; // to re-export the default export