Skip to content
This repository has been archived by the owner on Apr 6, 2021. It is now read-only.

@apply doesn't respect order of sibling declarations within same rule #35

Closed
sebszocinski opened this issue Mar 15, 2021 · 2 comments · Fixed by #155
Closed

@apply doesn't respect order of sibling declarations within same rule #35

sebszocinski opened this issue Mar 15, 2021 · 2 comments · Fixed by #155

Comments

@sebszocinski
Copy link

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

.some-div
  @apply bg-blue flex
  background: rgba(0,0,0,0.5)

app.css (Built)

.some-div
  background-color: blue
  display: flex
  background-color: rgba(0,0,0,0.5)

After JIT

app.sass

.some-div
  @apply bg-blue flex
  background: rgba(0,0,0,0.5)

app.css (Built)

.some-div
  background-color: rgba(0,0,0,0.5)
  background-color: blue
  display: flex
@adamwathan
Copy link
Member

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 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
@adamwathan
Copy link
Member

Should be fixed in v0.1.9 (hopefully! 🙈)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants