This repository has been archived by the owner on Oct 31, 2024. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Webpack Bundle Analyzer is a tool that would be useful to have in any project that cares about optimizing their bundle size. This setup by default generates a
report.html
insidedist
on the browser production build. I set theopenAnalzyer: boolean
option to be configured fromconfig/project.js
so that users can change it without editingkit
. If set to true, the report will be automatically opened in the users default browser after each build. If it would be better, I can remove the external configuration controls.