projectwallace / projectwallace/css-analyzer
Analyze use of `@layer` polyfill
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 366
- Forks
- 15
- Avg merge
- 3h 23m
- Merged PRs (30d)
- 3
Description
via @romainmenke https://bsky.app/profile/romainmenke.bsky.social/post/3mc3mdv5iwk2s
Not sure if to file this under atrules.layer.polyfills or selectors.layerPolyfills.{total,totalUnique,unique,uniquenessRatio,ratio}. Leaning towards the latter.
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 with the referenced Bluesky post and inspect the analyzer's existing atrules.layer.polyfills and selectors.layerPolyfills statistics to understand how similar metrics are organized. The issue does not name files, tests, or a specific change; done would require deciding where @layer polyfill usage belongs and defining the expected analysis and validation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css, typescript
- Domain
- analytics, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100