how to enforce browser compatibility? #1212
daniellacosse
started this conversation in
Ideas
Replies: 1 comment
-
It's definitely good practice to use Enforcing type-level constraints based on browser targets could be interesting. However, that would likely involve code-generation on our end, which is complexity that could potentially be avoided if we instead created a postCSS custom syntax that enabled stylint to work with VE. That would also be a non-trivial amount of effort though (unless there's an easier way). |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I'm in the process of migrating a project to vanilla-extract - really liking it - but I've realized I'm losing a lot of what I'd set up via stylelint. In particular, the blocking of CSS properties that aren't supported in my target browsers.
I think I'd get the same thing with some good e2e testing so it's not gonna block me, but I think it would be really cool if vanilla-extract enforced certain things at the type-level based on configs like browserslist
I may try to rig something temporary with CSS.supports so stay tuned
Beta Was this translation helpful? Give feedback.
All reactions