-
Notifications
You must be signed in to change notification settings - Fork 40
cannot use CSS variables #102
Comments
@aweary I ran into a similar issue, but with the In your case however, is there a reason you aren't using your variable directly in your tailwind config instead? The bracket syntax is supposed to be for one-off things, but your variable name suggests otherwise. I'm not the cops though 😉 |
@daronspence a CSS variable can still be useful for one-off use cases, a better example might be something like The brackets syntax says it's for "arbitrary values" so arbitrary would imply any value at all. It should really just make sure it parses according to the CSS grammar and pipe it through. |
@aweary Thanks for raising this! Right now the arbitrary value support is pretty curated, so each utility may or may not support it and may only support certain formats. I started really conservative with it because it's easy to loosen the restrictions. For padding I see no reason to not just allow any value at all, so we can definitely update this. In other cases we have to be more careful about supporting any value or we might "hit" the wrong utility plugin, like Again for padding though this is totally doable, there are no naming collisions or anything there so I'll update this one! |
Should be good now in v0.1.4 👍🏻 |
What version of @tailwindcss/jit are you using?
0.1.3
What version of Node.js are you using?
12.20.1
What browser are you using?
Chrome
What operating system are you using?
macOS
Reproduction repository
https://www.youtube.com/watch?v=4e7iksx-Zig
I'd expect that:
would generate something like
but seems like it just does nothing
The text was updated successfully, but these errors were encountered: