Build size info
See original GitHub issueWould it be useful to try and give a breakdown of the build size when you build? Sometimes I include a few libraries and the bundle size balloons out and I’m not too sure why, and with create-react-app wrapping webpack it’s a bit cumbersome to run these tools eg webpack-bundle-size-analyzer.
Is it worth looking into some way of displaying this when npm run build
is used, similar to how gzip size is shown now?
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Reducing the file size of your build - Unity - Manual
Keeping the file size of the built app to a minimum is important, especially for mobile devices or for app stores that impose...
Read more >Build Size - Log File - Unity Forum
When I create a new project and a new (empty) scene, the size will be 7KB. I have read that there is a...
Read more >Reduce your Unity Build Size with some quick shrinking Tips ...
Check out the Course: https://bit.ly/3i7lLtH-------Shrink your Unity3D project build size with a few simple tricks.
Read more >Reduce Unity Build Size - Unity Build Report - YouTube
In this video, I will show you how you can investigate your unity build size by investigating the unity build report.
Read more >Manual: Reducing the file size of your build - Unity
The first step in reducing the size is to determine which Assets contribute most to it, because these Assets are the most likely...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Seems source-map-explorer is a more accurate way of seeing built module size.
The data looks like this (from the visual tool).![source-map-explorer](https://raw.githubusercontent.com/danvk/source-map-explorer/master/screenshot.png)
@tbillington This sounds reasonable! I’ll close in favor of #798 but you are welcome to submit a pull request implementing what you suggested.