tailwind4-expert

To migrate from Tailwind v3 to v4, transition your design tokens into the new @theme CSS block and remove the tailwind.config.js file. This enables a pure CSS workflow powered by the Oxide engine for faster, zero-JS builds.

The Tailwind 4 Oxide engine processes design tokens defined within the @theme CSS block as native CSS variables. This CSS-first architecture eliminates JavaScript configuration, allowing you to model tokens directly in your stylesheet for faster builds.

The best way to configure container queries in Tailwind 4 is by using native CSS container query variants like @md: and @lg: directly in your markup. This leverages modern CSS capabilities without requiring plugin configurations.

Yes, Tailwind 4 works with React, Vue, and other frontend frameworks. It provides step-by-step migration guidance to maintain design system integrity across apps by applying CSS-first tokens and native container queries.

You should remove tailwind.config.js when upgrading to Tailwind 4 to adopt a CSS-first design system. Moving all tokens to the @theme CSS block enables a pure CSS workflow, leveraging the Oxide engine for zero-JS configuration and faster builds.

Yes, you can use 3D transforms with Tailwind 4 native CSS utilities. The framework's modern CSS architecture supports native container queries and 3D transforms, allowing you to implement complex visual effects directly within your design system.