GoogleChrome / GoogleChrome/lighthouse-ci
feat: bundlesize dashboard
- Dominant language
- JavaScript
- Stars
- 7.1k
- Forks
- 716
- PR merge metrics
- No merged PRs in 30d
Description
Lighthouse has already some great information on the size of all chunks into the application.
It would be nice to see those results in a dashboard where you can decide even a budget and keep track of the top 25/50/100 largest chunks, this will help detect regressions much faster.
Contributor guide
Research direction
Start by reviewing how Lighthouse currently exposes chunk-size information and how the project presents existing results. Define the dashboard, budget, and top-chunk requirements from the issue before identifying the relevant implementation and test entry points; done means regressions can be tracked against a chosen budget.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100