root
/
webpack
mirror of https://github.com/webpack/webpack.git
1
0
Fork 0
Code Issues Actions Packages Projects Releases Wiki Activity

Merge pull request #4762 from huy-nguyen/fix-documentation 

Fix indentation
This commit is contained in:
Tobias Koppers 2017-04-21 09:27:16 +02:00 committed by GitHub
parent 8aa8a7b63f 6124837c41
commit 38f9686a5d
2 changed files with 30 additions and 30 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

30
examples/common-chunk-and-vendor-chunk/README.md
View File

@ -3,31 +3,31 @@ This example shows how to create an explicit vendor chunk as well as a common ch
To better understand, here are the entry points and which utility modules they depend on:
- `pageA`
- `utility1`
- `utility2`
- `utility1`
- `utility2`
- `pageB`
- `utility2`
- `utility3`
- `utility2`
- `utility3`
- `pageC`
- `utility2`
- `utility3`
- `utility2`
- `utility3`
Given this configuration, webpack will produce the following bundles:
- `vendor`
- webpack runtime
- `vendor1`
- `vendor2`
- webpack runtime
- `vendor1`
- `vendor2`
- `common`
- `utility2`
- `utility3`
- `utility2`
- `utility3`
- `pageA`
- `pageA`
- `utility1`
- `pageA`
- `utility1`
- `pageB`
- `pageB`
- `pageB`
- `pageC`
- `pageC`
- `pageC`
With this bundle configuration, you would load your third party libraries, then your common application code, then your page-specific application code.

30
examples/common-chunk-and-vendor-chunk/template.md
View File

@ -3,31 +3,31 @@ This example shows how to create an explicit vendor chunk as well as a common ch
To better understand, here are the entry points and which utility modules they depend on:
- `pageA`
- `utility1`
- `utility2`
- `utility1`
- `utility2`
- `pageB`
- `utility2`
- `utility3`
- `utility2`
- `utility3`
- `pageC`
- `utility2`
- `utility3`
- `utility2`
- `utility3`
Given this configuration, webpack will produce the following bundles:
- `vendor`
- webpack runtime
- `vendor1`
- `vendor2`
- webpack runtime
- `vendor1`
- `vendor2`
- `common`
- `utility2`
- `utility3`
- `utility2`
- `utility3`
- `pageA`
- `pageA`
- `utility1`
- `pageA`
- `utility1`
- `pageB`
- `pageB`
- `pageB`
- `pageC`
- `pageC`
- `pageC`
With this bundle configuration, you would load your third party libraries, then your common application code, then your page-specific application code.