-
Notifications
You must be signed in to change notification settings - Fork 570
Output file size analyzer tool #982
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
Comments
I was pretty sure I've seen a tool or a script that does this, but after spending a few minutes searching, I couldn't find it now. Hopefully someone else can recall, find, or create one. It's not very hard to write a script, as the minifized .js file has one line per imported package. For non-GopherJS size analysis, I've used goweight. |
Thanks, I also had the same feeling yet found nothing, but decided to ask before I try to write something myself :) |
I am going to shelve this feature for the time being. I still think this would be a useful tool to provide, but it also adds a considerable maintenance burden, which we currently can't really afford. Also having thought about it a bunch, improving sourcemap support and using existing source map visualizers might be an all-around better solution. |
Is there a tool which can analyze GopherJS-generated JavaScript file and build a diagram of which packets contribute to the file size and through which dependencies they were pulled in? That is, something similar to https://github.com/webpack-contrib/webpack-bundle-analyzer, which can understand Go packages.
This is tangentially related #136, but is separate, since it's not about changing compiler as much as about understanding where file size comes from.
The text was updated successfully, but these errors were encountered: