projectwallace / projectwallace/css-analyzer
Improve size reporting
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 366
- Forks
- 15
- Avg merge
- 3h 23m
- Merged PRs (30d)
- 3
Description
Knowing the actual size of the CSS string is only halfway useful. For comparison of data it'd be way more useful if we could 'normalize' the size, like minifying it before sizing. It will take up some extra CPU + an extra dependency, so I'm not sure if it should be part of this library.
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
The issue names no files, tests, or entry points. Start by locating the existing CSS size-reporting implementation and dependency configuration, then trace how size statistics are exposed. Clarify whether normalized size should be added alongside the current value and what minification behavior and dependency constraints define completion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css, typescript
- Domain
- analytics
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100