-
-
Notifications
You must be signed in to change notification settings - Fork 611
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: support webpack-bundle-analyzer with CLI #1838
Comments
Yes:
|
to respect built-in options |
This issue had no activity for at least half a year. It's subject to automatic issue closing if there is no activity in the next 15 days. |
Bump |
This issue had no activity for at least half a year. It's subject to automatic issue closing if there is no activity in the next 15 days. |
Bump |
This issue had no activity for at least half a year. It's subject to automatic issue closing if there is no activity in the next 15 days. |
Let's start working on next first before adding more fetures. |
Issue was closed because of inactivity. If you think this is still a valid issue, please file a new issue with additional information. |
Hi, can you please providde a basic idea on how to proceed with this |
Like the basic implimentation would be to create a plugin webpack-bundle-analyzer can you tell me about how can i go about the analyzing part, like the webpack functions or data to be used |
|
So Ill then start reffering to https://github.com/webpack-contrib/webpack-bundle-analyzer |
As per what I see, we already have a --analyze flag added, which loads the webpack-bundle-analyzer plugin. I will try to add the plugin to webpack itself and then load it with the same. |
Is your feature request related to a problem? Please describe.
We can have an
analyze
flag which invokes webpack-bundle-analyzer as bundle information is crucial limiting size and determining potential bloatsDescribe the solution you'd like
we can list it in peer dep and use the analyzer which the user has installed instead of shipping out of the box to keep package size low.
Describe alternatives you've considered
Additional context
/cc @evilebottnawi
The text was updated successfully, but these errors were encountered: