While it would be beneficial to open a bug for CleanCSS, I would have to make a reduced example of compiled TailwindCSS (customized obviously). It's effort that I would rather not have to do since I _assume_ that the Tailwind compiler optimizes it's output except for minification.

Over the last few days while working on an upcoming blog post I've performed quite the yak shaving:

1. I wanted to use `@layer` in a #CSS demo (ironically one showing that it doesn't solve this particular use case).
2. My auto #CSP setup using #JSDom and #CleanCSS failed to parse `@layer`.

#ModernCSS Code Snippets — It has a few rough edges, but the core idea of showing a variety of #CSS snippets with a before/after showing the “old” way to do something versus the “new” way is neat || #WebDev #WebDevTips #CleanCSS bit.ly/4sqnkIa

Magical Coding Tips Part #3: CSS Background Shorthand ✨
Write less, style more — master background magic at javidev (link in my profile).
mystic.js

#CSSShorthand #BackgroundCSS #FrontendTips #CodeSmart #WebStyling #DevShortcuts #CleanCSS #HTMLMagic #LearnFrontend #WebCraft

Magical Coding Tips Part #5: Padding CSS Shorthand 🧙‍♂️
Simplify your spacing spells with one clean line — explore more at javidev (link in my profile).
mystic.js

#CSSPadding #ShorthandCSS #SpacingTips #FrontendMagic #CodeBetter #WebStyle #CleanCSS #DevHacks #UIBasics #WebTips

3. I upgraded #CleanCSS.
4. I removed #JSDom and replaced it with #parse5, which works with `@layer`.
5. I wanted to use `Object.groupBy` here which requires `target: "ES2024"` in #TypeScript.
6. Therefore I needed to upgrade TS.
7. Upgrading TS broke #Karma for reasons I couldn't understand.

cleancss

cleancss