Skip to content

docs: clarify splitChunks request defaults #8332

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.

Sign up for GitHub

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

Open
rajanpanth wants to merge 1 commit into
base: main
Choose a base branch
from
+8 −0
Open

docs: clarify splitChunks request defaults #8332

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
8 changes: 8 additions & 0 deletions src/content/plugins/split-chunks-plugin.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,6 +46,14 @@ Webpack will automatically split chunks based on these conditions:

When trying to fulfill the last two conditions, bigger chunks are preferred.

T> The default request limits are heuristic guardrails, not HTTP/1-specific
recommendations. Browsers and transports such as HTTP/2 can handle many parallel
requests, but extra chunks still add scheduling, header, cache lookup, parsing,
and evaluation overhead. If your app benefits from more granular chunks, adjust
[`splitChunks.maxAsyncRequests`](#splitchunksmaxasyncrequests) and
[`splitChunks.maxInitialRequests`](#splitchunksmaxinitialrequests), then measure
the result for your users.

## Configuration

Webpack provides a set of options for developers that want more control over this functionality.
Expand Down
Loading