Tailwind CSS 4.3.4 Adds @tailwindcss/turbopack, a Turbopack Loader for Next.js, and Fixes Vite Plugin, Watch Mode and macOS Binary Issues

Overview

Tailwind CSS v4.3.4 adds a new package, @tailwindcss/turbopack, which the release notes describe as “a Turbopack loader for using Tailwind CSS with Next.js”. The release was published on 2 November 2026 at 21:16 UTC, according to the timestamp on the same release page. The rest of the notes are a long list of fixes covering watch mode, the Vite plugin, class extraction and canonicalization.

The Turbopack loader

The package comes from pull request #20367, titled “Add @tailwindcss/turbopack loader” and opened by timneutkens. Its description says the package is based on the webpack loader and that the change documents Turbopack installation, configuration and loader options. The pull request page shows it was merged by RobinMalfait after being opened on July 30, 2026, with the merge shown as July 31, 2026.

The package README describes it as “A Turbopack loader for Tailwind CSS v4.” It is installed with npm install @tailwindcss/turbopack and is wired in through the turbopack.rules setting in next.config.js, where a *.css rule lists @tailwindcss/turbopack as its loader. A CSS file then imports Tailwind with @import 'tailwindcss';.

The README lists two loader options:

• base: the base directory to scan for class candidates, which defaults to the current working directory.
• optimize: whether to optimize and minify the output CSS, which defaults to true in production mode.

Separately, the release notes list a fix that makes @tailwindcss/turbopack and @tailwindcss/webpack rebuild when the input CSS changes. They give the example that next dev with Turbopack no longer serves the CSS of the previous edit.

Other changes in the release

Under “Fixed”, the release notes include several items touching tooling integrations:

• Watch mode now detects changes to symlinked @source files whose real paths are not otherwise scanned.
• @tailwindcss/vite no longer crashes on every edit under Vite’s experimental bundledDev mode, and no longer forces full-page reloads for scanned files that Vite does not handle as modules, such as .php files.
• @tailwindcss/oxide falls back to WASM on platforms without native bindings.
• Automatic source detection respects negation-based .gitignore files.
• The standalone macOS binaries now have a valid code signature, so that macOS 27 no longer kills them at launch.

Other entries concern CSS handling and class extraction. Variants using @scope now wrap generated utilities instead of nesting inside them, and class candidates are extracted from Ruby %w and %W literals that use angle brackets or custom delimiters. Many entries are marked “Canonicalization”, covering how utilities are converted to or collapsed into equivalent forms, per the same release notes.

What We Don’t Know

The release notes and README do not say how the loader compares with the existing @tailwindcss/postcss approach in build speed or output, and no benchmark figures appear in the sources reviewed. The sources also do not state which Next.js versions the loader is intended to support.