-
-
Notifications
You must be signed in to change notification settings - Fork 484
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
Feature request: Generate analysis report file #194
Comments
Hi @valscion, sorry it's been such a long time since I drafted this issue.
ExampleWe integrated this with Still, suggestions and discussion are super welcome 🙏😀 |
this looks great. how can I test this? |
@burgalon Just like the example PR mentioned above jasperck/react-gobang#3
then it will generate a analysis json file after the build. |
This looks amazing and is pretty much exactly what I've been trying to do as well! |
This sounds like a neat feature. I haven't replied yet as I'm torn on opening up the generated graph data JSON to be a part of the public API. I'm still keen on trying to separate the treemap visualization from the data generation on an architecture level (see #97 for my last failed attempt). If I could get the visualization separated neatly from the data generation, adding new reporters such as "just write the data to a file" would have better support instead of needing a special flag to output the graph data. So while I agree that enabling this sort of feature would be useful, I'm not sure if adding a new flag is the way to go. |
@rafael-anachoreta Thanks😂 The whole flow was done by |
@valscion Cool, I agree separating data generation and visualization on architecture level should be a better way to achieve the goal! If this is in the roadmap then I put my hands up for it rather than extending a new flag. Decouple should leads to more flexibility here. |
Thanks. I'm not sure if there's any clear contribution opportunities here, though — doing large changes would then be a review burden to maintainers and would likely end up as wasted effort. I might have time and motivation to try the splitting again in the future |
Hi ~ Because my work need to show this data on a dashboard, I have to generate the visualization data and crop it. I've implemented this feature on my fork and used it for production. I think my fork is just a short-term solution and want to know if Like @jasperck, I can contribute to it, small changes, or separate visualizations and data, or add more visualizations. |
Hello 👋 just wanted to register my interest in an option for a machine readable bundle size breakdown report as well. Just wanted to check in case you'd changed your mind at all about making the current JSON representation public? Regardless, thanks very much for maintaining |
I doubt that I will be doing work related to that in the near future
I no longer have strong feelings about this, given I haven't got work done on the splitting done at all recently. Does @th0r have opinions about the JSON representation being public? |
Issue description
Thanks for the awesome plugin, it truly helps us analyzing how our bundles had been built. Recently, I'm looking to analyze size of bundles in background or on CI.
webpack-bundle-analyzer
does great help for creating and storing thestats
file fromwebpack
, which gives me the opportunity to tweak the data in file. Butwebpack-bundle-analyzer
only store the origin stats file, if we in some cases need information likegzip size
, then there's no chance here.In this case, the data which
report.html
used seems to be more valuable. Thus I think it would be awesome to makewebpack-bundle-analyzer
possible to generates and stores the data.Please feel free to close this if it's not something this plugin should response for. Otherwise, I'd be happy to create a PR for this. Also, suggestions and discussion are super welcome 🙏😀
The text was updated successfully, but these errors were encountered: