`analyzeBundle` flag
See original GitHub issueThank you for this amazing project!
I was wondering if there was any interest in adding a analyzeBundle
flag, backed by the awesome webpack-bundle-analyzer plugin. Here are some use cases:
- This would give us an indication of how large our bundle is.
- What packages we are using and how much memory each package is taking up.
- Answers to questions like: “Did we accidentally include
aws-sdk
in project dependencies?”
Part of me feels like this maybe out of scope of this project, but since we don’t have direct access to override the default webpack.config.js
file, this seems like the best next step. Happy to brainstorm other ideas as well! I’m also happy to make a PR for this if necessary!
Issue Analytics
- State:
- Created 2 years ago
- Reactions:9
- Comments:13 (6 by maintainers)
Top Results From Across the Web
Webpack Bundle Analyzer - GitHub
Webpack plugin and CLI utility that represents bundle content as convenient interactive zoomable treemap - GitHub - webpack-contrib/webpack-bundle-analyzer: ...
Read more >Build Analysis - SurviveJS
To make webpack emit analysis information, you should set the --json flag and pipe ... It's possible to analyze bundle dependencies in a...
Read more >How to configure webpack-bundle-analyzer for react?
Run npm install --save-dev webpack-bundle-analyzer to install webpack-bundle-analyzer · Add a --stats flag at the end of "build" script command ...
Read more >Production - Parcel
You can use the --no-optimize CLI flag to disable minification and other optimizations if ... Parcel includes some tools to help you analyze...
Read more >How to use the webpack bundle analyzer - Jakob Lind
To run webpack in production mode production mode, you pass in the mode flag like this. webpack --mode production. Webpack bundle analyzer react....
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 FreeTop 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
Top GitHub Comments
Thank you. Yeah option 2 makes more sense. I would prefer if we defaulted the path to something sensible so they don’t have to set it, unless they really wanted to. Could we put this into the
.serverless
or.webpack
(I’m not sure if serverless-webpack still uses this) directory?@jayair, did you get a chance to review #269?