-
-
Notifications
You must be signed in to change notification settings - Fork 27k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Add some analyze script for npm packages #798
Comments
Agree this would be nice but not sure what approach would be most useful. |
stats.json also sounds good, just need to view what kind of info each
produces so we see what kind of info suits the majority. Will look into it.
|
This is what we do at |
Is this still a discussion? I was thinking of trying and implementing what @mxstbr mentioned. |
Feel free to send a PR! |
I added webpack bundle analyzer since it gives you a lot more information if we want to run stats on our bundle. I sent first PR #2359, however CI is failing on node 6. Any clue? |
Guys, I highly recommend the Bundle Buddy tool from @samccone https://twitter.com/franklinjavier/status/931324987654443008?s=17 |
A bit of a hack, but you can create your own very simple script that appends the webpack-bundle-analyzer plugin to the config without ejecting. I wrote about it here: #3518 |
Closing in favor of more recent discussion in #1858. |
Hi,
I would love to have some anylyze script that would print out size for individual package bundled with webpack.
Something like I read here: http://stackoverflow.com/questions/34700844/how-can-i-find-out-the-size-of-the-included-packages-with-webpack-or-npm
The text was updated successfully, but these errors were encountered: