Note that @layer CSS at-rule will not be output.
#1892
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Returning to Tailwind after using native `@layer` system, I lost an hour of work thinking that something with my PostCSS setup was stripping my `@layer` at-rules. I think the at-rule has matured to the point where people that haven't been using Tailwind for a while might expect to see it output. I see v4 will output this, but v3 simply reorders the rules for maximum compatibility. I have read the documentation here multiple times and I feel if this statement was here it would click in my head sooner that Tailwind v3 does not actually output the `@layer` at-rules and instead tracks and reorders them.
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
If anyone stumbles on this, here's a helpful article that talks about what goes on under the hood on how Tailwind handles @layer https://emamoah.medium.com/using-native-css-cascade-layers-with-tailwindcss-cb11af266104 |
|
Hey! Thanks for the PR but we've since moved to the v4 docs which does not face the same issue anymore so going to close this one. Sorry for the long wait for a response here, we've all been pretty busy working on the v4 release stuff and these PRs unfortunately incurred a much longer than expected wait time. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Returning to Tailwind after some time of using the native
@layersystem, I lost an hour of work thinking that something with my PostCSS setup was stripping my@layerat-rules. I think the at-rule has matured to the point where people that haven't been using Tailwind for a while (or never had) might expect to see it output. I see v4 will output this, but v3 simply reorders the rules for maximum compatibility.I have read the documentation here multiple times and I feel if this statement was here it would click in my head sooner that Tailwind v3 does not actually output the
@layerat-rules and instead tracks and reorders them. It was only when I started testing the outputs in the playground did I realize this distinction.Feel free to reword and thanks for the otherwise great docs and css framework!