Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update dependency-graph.md #4305

Closed
wants to merge 1 commit into from
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions src/content/concepts/dependency-graph.md
Original file line number Diff line number Diff line change
Expand Up @@ -16,4 +16,10 @@ Any time one file depends on another, webpack treats this as a _dependency_. Thi
When webpack processes your application, it starts from a list of modules defined on the command line or in its configuration file.
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.

Sometimes it is very helpful to visualize the dependency graph using tools like `webpack-visualizer`. You can install it by:

``` bash
npm install webpack-visualizer-plugin
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The latest version was published 4 years ago, and it won't work with webpack 5 chrisbateman/webpack-visualizer#71.

```

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.