From 38e640b54bbda17d19b3d7fcc9fb6e6ce8fe6743 Mon Sep 17 00:00:00 2001 From: EugeneHlushko Date: Thu, 6 Sep 2018 23:38:36 +0300 Subject: [PATCH 1/2] docs(concepts) Update dependency graph concepts page --- src/content/concepts/dependency-graph.md | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/src/content/concepts/dependency-graph.md b/src/content/concepts/dependency-graph.md index bebc98236083..daffd90a5f71 100644 --- a/src/content/concepts/dependency-graph.md +++ b/src/content/concepts/dependency-graph.md @@ -3,11 +3,17 @@ title: Dependency Graph sort: 9 contributors: - TheLarkInn + - EugeneHlushko +related: + - title: HTTP2 Aggresive Splitting Example + url: https://github.com/webpack/webpack/tree/master/examples/http2-aggressive-splitting + - title: webpack & HTTP/2 + url: https://medium.com/webpack/webpack-http-2-7083ec3f3ce6 --- Any time one file depends on another, webpack treats this as a _dependency_. This allows webpack to take non-code assets, such as images or web fonts, and also provide them as _dependencies_ for your application. When webpack processes your application, it starts from a list of modules defined on the command line or in its config file. -Starting from these _entry points_, webpack recursively builds a _dependency graph_ that includes every module your application needs, then packages all of those modules into a small number of _bundles_ - often, just one - to be loaded by the browser. +Starting from these [_entry points_](/concepts/entry-points/), webpack recursively builds a _dependency graph_ that includes every module your application needs. Then packages all of those modules into a small number of _bundles_ - often, just one - to be loaded by the browser. -T> Bundling your application is especially powerful for *HTTP/1.1* clients, as it minimizes the number of times your app has to wait while the browser starts a new request. For *HTTP/2*, you can also use Code Splitting and bundling through webpack for the [best optimization](https://medium.com/webpack/webpack-http-2-7083ec3f3ce6#.7y5d3hz59). +T> Bundling your application is especially powerful for _HTTP/1.1_ clients, as it minimizes the number of times your app has to wait while the browser starts a new request. For _HTTP/2_, you can also use [Code Splitting](/guides/code-splitting/) to achieve best results. From a584304d0adde4446840630fa52778ded05bca50 Mon Sep 17 00:00:00 2001 From: EugeneHlushko Date: Fri, 7 Sep 2018 09:45:43 +0300 Subject: [PATCH 2/2] docs(concepts) Dependency graph minor tweak --- src/content/concepts/dependency-graph.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/concepts/dependency-graph.md b/src/content/concepts/dependency-graph.md index daffd90a5f71..acc65b2c0517 100644 --- a/src/content/concepts/dependency-graph.md +++ b/src/content/concepts/dependency-graph.md @@ -14,6 +14,6 @@ related: Any time one file depends on another, webpack treats this as a _dependency_. This allows webpack to take non-code assets, such as images or web fonts, and also provide them as _dependencies_ for your application. When webpack processes your application, it starts from a list of modules defined on the command line or in its config file. -Starting from these [_entry points_](/concepts/entry-points/), webpack recursively builds a _dependency graph_ that includes every module your application needs. Then packages all of those modules into a small number of _bundles_ - often, just one - to be loaded by the browser. +Starting from these [_entry points_](/concepts/entry-points/), webpack recursively builds a _dependency graph_ that includes every module your application needs, then bundles all of those modules into a small number of _bundles_ - often, just one - to be loaded by the browser. T> Bundling your application is especially powerful for _HTTP/1.1_ clients, as it minimizes the number of times your app has to wait while the browser starts a new request. For _HTTP/2_, you can also use [Code Splitting](/guides/code-splitting/) to achieve best results.