You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 6, 2021. It is now read-only.
There are times where you still want to use good old CSS and previously I would add these under my @apply statements, and they'd be added to the bottom of the built css file and therefor override tailwind, but with jit they are being added to the top. eg:
Disclaimer: I know I can do this manual css using tailwinds bg-opacity-50 it's just an example...
Hey thanks for reporting! We know about this issue and will work on it soon 👍🏻 Updating the title just to make it easier to remember what this one is about when I see it in the list.
adamwathan
changed the title
Additional classes are added to the top of the built css and therefor overwritten@apply doesn't respect order of sibling declarations within same rule
Mar 22, 2021
There are times where you still want to use good old CSS and previously I would add these under my
@apply
statements, and they'd be added to the bottom of the built css file and therefor override tailwind, but with jit they are being added to the top. eg:Disclaimer: I know I can do this manual css using tailwinds
bg-opacity-50
it's just an example...Before JIT
app.sass
app.css (Built)
After JIT
app.sass
app.css (Built)
The text was updated successfully, but these errors were encountered: