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

add splitChunks.minSizeReduction #14516

Merged
merged 1 commit into from Oct 19, 2021
Merged

Conversation

sokra
Copy link
Member

@sokra sokra commented Oct 19, 2021

What kind of change does this PR introduce?
feature

Did you add tests for your changes?
yes

Does this PR introduce a breaking change?
no

What needs to be documented once your changes are merged?

  • splitChunks.minSizeReduction specifies the minimum size reduction to the whole compilation needed for creating a new chunk.
    • splitChunks.minSizeReduction and splitChunks.minSize need to be fulfilled for a chunk to be created. You may want to reduce minSize when using minSizeReduction

@webpack-bot
Copy link
Contributor

webpack-bot commented Oct 19, 2021

For maintainers only:

  • This needs to be documented (issue in webpack/webpack.js.org will be filed when merged)
  • This needs to be backported to webpack 4 (issue will be created when merged)

@sokra sokra force-pushed the feature/split-chunks-size-reduction branch from 81e8324 to 3d3c65f Compare October 19, 2021 10:35
@webpack-bot
Copy link
Contributor

Thank you for your pull request! The most important CI builds succeeded, we’ll review the pull request soon.

@sokra sokra merged commit 92cd284 into main Oct 19, 2021
@sokra sokra deleted the feature/split-chunks-size-reduction branch October 19, 2021 12:47
@webpack-bot
Copy link
Contributor

I've created an issue to document this in webpack/webpack.js.org.

@AllanOricil
Copy link

@sokra could you give an example to explain when I should use this? Thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants