🫧Bregtje🫧 · Apr 18

Huh no, didn’t know they exist..? So no, not yet but I’m very curious now! Does it work on every browser?

ArthurJ · Apr 19

Built a css library around them

Jake Lazaroff · Apr 18

yup, they’re pretty great for CSS resets and base styles

Juan Diego Rodríguez · May 19

Use them all the time in demos to separate the basic styling from what I want to show :)

Mary Baum · Apr 19

I think I want to know more. Course ultimately the CSS I use regularly will have to get supported in theme.json

Script Raccoon · Apr 19

I don't need them because every serious project uses a component framework anyway so that's that. Styles are scoped in Svelte and Vue.

Adam Argyle · May 1

Yep, for my whole site nerdy.dev

romainmenke · May 19

Actually stopped using them because we have full control over all styles in our projects. So we don't need the ability to push a group of styles into their own cascade layer. We found that specificity and source order are more nuanced tools giving us more detailed control.

benteh · Apr 18

they're scary!

Emmie Päivärinta · May 1

I just wish you could change where un-@layer'ed styles end up in the stack. With 3rd party styles, especially with css-in-js, you end up with styles taking precedence over all your @layer'ed styles, and there's nothing to do about it.

Steve Fulghum · Apr 19

I've tried integrating them into our CSS stack, but keep running into blockers. During my latest attempt, I found the CSS-in-JS solution from our third-party component library is effectively incompatible. I burned a lot of time writing plugin that would wrap its CSS output in a layer to no avail.

Manuel Matuzović · May 19

Yes! fokus.dev/tools/css-bo...

Zell Liew · May 1

Yep. Pretty useful for overwriting stuff