Web Dev · by Rizky Pratama · 2026-10-14

Baseline tooling is finally making 'can I use this CSS feature' way less painful

Been integrating Baseline status checks into our CI and it's quietly one of the best DX improvements in frontend tooling lately. No more manually checking caniuse for every new CSS feature before using it. Anyone else adopted this in their workflow yet?

0 sparks · 9 comments

Comments

Quiet Noodle · 0 likes

this has saved me so many 'why is this broken in safari' debugging sessions already, genuinely underrated feature

Jasmine Cruz · 0 likes

wish more css frameworks shipped baseline-aware linting out of the box by default honestly

Siti Lestari · 0 likes

container queries + has() selector finally feeling safe to use in prod because of this kind of tooling is a huge unlock

Maja Wiśniewska · 0 likes

do you have the eslint/stylelint config for this handy? would love to copy your setup

Isha Menon · 0 likes

seconding this request, been meaning to set it up for weeks

Faisal Al Saud · 0 likes

safari is always the asterisk in these baseline widely available labels in my experience lol, still test manually there

Maya Putri · 0 likes

as someone supporting enterprise clients stuck on old browsers this stuff is less useful for us sadly, still stuck polyfilling everything

Siti Lestari · 0 likes

its a small thing but reduces so much cognitive load during code review, no more googling compat tables mid PR

Sophie Gagnon · 0 likes

genuinely one of the more boring but high impact web platform improvements in a while, love to see it