Output file size analyzer tool
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 13.2k
- Forks
- 573
- PR merge metrics
- No merged PRs in 30d
Description
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 https://github.com/gopherjs/gopherjs/issues/136, but is separate, since it's not about changing compiler as much as about understanding where file size comes from.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the requested GopherJS-generated JavaScript analysis and related issue #136, then compare the dependency and visualization behavior of webpack-bundle-analyzer. Done means a usable tool can show which Go packages contribute to output size and the dependency paths that pulled them in.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, javascript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100