Editor/IDE/linting support for deleting dead css
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- css, typescript
Research direction
The issue names no files, tests, or entry points; first inspect the repository structure and existing CSS-blocks tooling before defining the scope. Clarify whether the desired result is an editor/IDE extension, a linter, or both, and agree on how unused CSS should be detected and what a completed implementation must demonstrate.
Written by the indexing model from the issue text.
Description
Css-blocks seems really awesome, and on further investigation, I think it will be the GOTO solution for css once it has reached 1.0 status
One thing I am curious about - I know css blocks will remove unused css - this is awesome so your utility classes can be there if you need them, but don't cause un-necessary bloat.
However, if you are refactoring large amounts of css, it seems to me we'd also be interested in removing the code from the codebase altogether. The best solution in my eyes would be an editor/ide extension that highlights unused/dead css, along with a linter that can help you clean up the whole codebase or evaluate its cleanliness.
Will this eventually be something that's included in the css-blocks experience?
- Dominant language
- TypeScript
- Stars
- 6.3k
- Forks
- 154
- PR merge metrics
- No merged PRs in 30d
Contributor guide
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.
More from linkedin/css-blocks
-
Difficulty 3/5 1-2 days Newbie friendliness 30/100
linkedin/css-blocks#592 ·
-
Difficulty 5/5 Over a week Newbie friendliness 10/100
linkedin/css-blocks#590 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
linkedin/css-blocks#563 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 5/100
linkedin/css-blocks#562 · 2 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
linkedin/css-blocks#555 ·
All issues in linkedin/css-blocks
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
copse-dev/agent-pane#2953 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug clawsweeper:linked-pr-open clawsweeper:needs-live-repro clawsweeper:no-new-fix-pr impact:message-loss issue-rating: 🐚 platinum hermit P2 regression
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·