Tailwind CSS v3 Content Configuration Transition from Purge

Transitioning to the JIT Engine

The shift from Tailwind CSS v2 to v3 integrated the Just-in-Time (JIT) engine as the default compiler. This architectural change replaced the legacy runtime engine, which generated a comprehensive set of utility classes and then purged unused styles during the build process.

Configuration Boundary

In v3, the purge configuration key was replaced by the content array. The JIT engine relies on this array to scan templates and generate only the CSS actually used in the markup, rather than filtering a pre-generated list.

When migrating legacy configurations, there is uncertainty regarding how the engine handles dynamic class strings that were previously compatible with the v2 purge mechanism but may not be detectable by the v3 static analysis scanner.

• Does the v3 content array support the same regex-based filtering options available in the v2 purge configuration?
• What is the recommended approach for ensuring dynamic class constructions are not omitted by the JIT scanner without bloating the final bundle?