feat(ui): adding bundle analyzer for prod and dev #15749
Merged
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.
this adds the ability for developers to compare bundle optimizations. when analyzing in develop mode (read:
yarn start
), assets are uncompressed and can be viewed athttp://localhost:9998
. When in production mode (read:yarn build
), the analysis can be reached by openingbuild/bundle-report.html
.as a point of order, remember that file size isn't as important from a network resource perspective, and that many small files is fine (production will start running http2 soon to remove much of the overhead of asset handshakes), but that large files slow down the time to first render + interaction by increasing time spent parsing the file (read: its an interpreted language). Best case scenario is to send a small file with only enough code to represent the current view, and to start loading everything else while the user clicks around.