Lazy loaded color variables is not defined in Chrome DevTools #12062
Replies: 1 comment 2 replies
-
|
Given that the HTML element has the styles applied and everything else is otherwise working this is not a Tailwind problem but one with Chrome DevTools. I'd file a browser bug for this but I can't reproduce this one myself. Do you have any kind of reproduction? |
Beta Was this translation helpful? Give feedback.
2 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.
Uh oh!
There was an error while loading. Please reload this page.
-
What version of Tailwind CSS are you using?
v3.3.3
What build tool (or framework if it abstracts the build tool) are you using?
vite 4.4.9, qwik 1.2.11
What browser are you using?
Chrome
What operating system are you using?
Ubuntu, Debian
Reproduction URL
Minimal reproducible example
Describe your issue
I'm trying to lazily load some CSS variables (mostly colors) to be used by Tailwind CSS.
This is part of my tailwind.config.js file:
And this is the colors.css file that is loaded when page loads in production. It's not part of the build:
And when I run my project, I can see that colors.css is loaded, and I can see that the HTML element has these styles applied to them (via Tailwind's compiled styles):
Yet when I hover over var(--color-1) the Chrome DevTools tells me that the
variable is not defined.Beta Was this translation helpful? Give feedback.
All reactions