FAQ: TailwindCSS v4 New Syntax and Its Compatibility with Other Systems #17251
rozsazoltan
started this conversation in
Show and tell
Replies: 0 comments
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.
-
Hi everyone! I'm more active on Stack Overflow. I've been using TailwindCSS for years and closely following the community. With the introduction of v4, I noticed a lot of chaos; many breaking changes have made previously well-established workflows obsolete.
However, despite the changes, the new features in TailwindCSS v4 are great and genuinely simplify our work in many areas.
I'd like to summarize some of the available Q&A references here in the TailwindCSS repository as well. I can only focus on the answers I've provided here, but there are many other useful Q&A discussions available; especially from Wongjn.
Guides
CSS-first
@themevs@layer themevs:root*and when should I use:root, :hostas the parent selector?@themeor@theme inline?TailwindCSS with other systems
Breaking changes
@tailwinddirectivesDark mode
Interesting facts
@screenhow to useprint:andscreen:to the new@themestyle?@custom-variantexamples: How to access all the direct children of a div in Tailwind CSS?Custom namespaces and utilities
transition-*with custom--transition-*namespaceclip-box-*utilitytext-stroke-*utilitywriting-modeclipcirc-*utilityh-{screen,dvh,lvh,full}-minus-*andw-{screen,full}-minus-*utilitiesbg-position-{x,y}-*utilitiesanimate-{repeat,duration}-*utilities--border-style-*namespacebg-opacity-*utility no longer exists as of v4 - how could it still be created?IDE - VSCode
Beta Was this translation helpful? Give feedback.
All reactions