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. - ThreadSky

About ThreadSky

fulghum.digital • 47 days ago

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.

Comments

cssweekly.com•18 days ago

Thanks so much for sharing this, Steve! It's a perfect fit for 3rd party plugins and widgets, but in reality, it's challenging to make it work. 🙁

Did you try with @import? And would a layer attribute for the tag help with your use case?

fulghum.digital•17 days ago

Unfortunately the library we're using handles all the style management, and I couldn't (quickly) find a way to change how it adds everything.

Emotion.js is under the hood. I was able to build a rudimentary plugin to wrap the styles with @layer, but only some appended styles were affected.

fulghum.digital•17 days ago

Something else in the library was interfering with how that plugin was being run and styles added. Too bad. But I ran out of time to investigate and had to move on to another task.

fulghum.digital•17 days ago

@layer has been great when I've used it elsewhere, and I'd like to use it at my company. But until toolchains fully support it (they should), it'll be tough to convince developers to spend the time implementing it.

Posting Rules

Be respectful to others
No spam or self-promotion
Stay on topic
Follow Bluesky's terms of service

Comments

Posting Rules

Reply