Replies: 1 comment 1 reply
-
You could consider using module.exports = {
theme: {
extend: {
colors: {
foo: 'color-mix(in oklch, light-dark(#fff, #000) calc(<alpha-value> * 100%), transparent)', |
Beta Was this translation helpful? Give feedback.
1 reply
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.
Uh oh!
There was an error while loading. Please reload this page.
-
As far as I'm aware, this isn't currently possible.
I'm trying to handle multiple dynamic themes in my app, as well as light/dark modes. My approach is to define my theme palettes in css variables and add them to tailwind.config, that way I can make them change based on both color-scheme and some custom attributes. The issue arises when I try to use the recent light-dark() function, to avoid defining them twice with media queries. Tailwind expects variables to be simply color channels for them to work with the opacity modifier.
I see two options right now, which is to either define all my themes "twice" (in size, for the media query), or I can just use light-dark() directly and lose the ability to use opacity modifiers. I'll probably go with the first option, but it's a very minor annoyance.
Thanks for looking at this 😀.
Beta Was this translation helpful? Give feedback.
All reactions