@tailwindcss/turbopack
4.3.4 · 2 Nov 2026MIT2.1M / weekRepositoryHomepagenpmAtom feed
Latest releases
4.3.4
2 Nov 2026Add
@tailwindcss/turbopack, a Turbopack loader for using Tailwind CSS with Next.jsEnsure watch mode detects changes to symlinked
@sourcefiles whose real paths aren't otherwise scannedEnsure variants using
@scopewrap generated utilities instead of nesting inside them
Added
Add
@tailwindcss/turbopack, a Turbopack loader for using Tailwind CSS with Next.js
Fixed
Ensure watch mode detects changes to symlinked
@sourcefiles whose real paths aren't otherwise scannedEnsure variants using
@scopewrap generated utilities instead of nesting inside themEnsure nested
@scoperules preserve their scoping semantics when flattenedPreserve declarations directly inside
@scopeby wrapping them in:where(:scope)Ensure generated utilities include a space in empty
var()fallbacks (e.g.var(--tw-blur,)→var(--tw-blur, ))Canonicalization: Convert arbitrary breakpoint and container query variants to named equivalents (e.g.
max-[64rem]:flex→max-lg:flex)Prevent
@tailwindcss/vitefrom crashing on every edit under Vite's experimentalbundledDevmodeEnsure
@tailwindcss/oxidefalls back to WASM on platforms without native bindingsExtract class candidates from Ruby
%wand%Wliterals using angle brackets or custom delimiters (e.g.%w<flex>,%w|flex|), including in Slim and Haml templatesPreserve whitespace in
--default(…)values in functional@utilitydefinitions (e.g.--default(box alphabetic)no longer becomesboxalphabetic)Ensure automatic source detection respects negation-based
.gitignorefiles (e.g./*followed by!/…patterns)Ensure root
theme('…')namespace lookups in JavaScript plugins and config files return the full namespace object instead of the value of itsDEFAULTkeySkip ignored directories when generating watch globs instead of walking their contents on every rebuild
Drop invalid UTF-8 candidates during class detection
Prevent
@tailwindcss/vitefrom forcing full-page reloads for scanned files that Vite does not handle as modules (e.g..phpfiles)Canonicalization: Don't merge utilities that reference different theme variables set to CSS-wide keywords like
unsetDon't generate utilities when a modifier is used that would otherwise be silently ignored (e.g.
rounded-sm/[5],shadow-sm/foo,stroke-2/50)Preserve
and,or, andnotinside selectors insupports-[…]variants (e.g.supports-[selector(a:not(.foo))]:flex)Don't warn about Angular's
::ng-deepand:host-context()when optimizing CSSDon't generate CSS for candidates containing an empty additional modifier (e.g.
bg-red-500/50/andgroup-hover/foo//bar:flex)Ensure
min-*,max-*, and container query variants with decimal values are sorted numerically (e.g.min-[40.25rem]beforemin-[40.5rem])Ensure CSS comments ending with
\*/are closed correctly instead of swallowing the CSS that follows (e.g./* C:\temp\*/)Improve style invalidation performance of
group-*andpeer-*variantsEnsure cached compilers release their
loadModuleandloadStylesheetcallbacks after compilationCanonicalization: Preserve
&when moving a pseudo-element into*or**(e.g.[&_::before]:flex→**:[&::before]:flex)Ensure the
Set.prototype.intersectionpolyfill incanonicalizeCandidates(…)returns the intersection instead of the first set on Node.js < 22Canonicalization: Ensure inline
theme(…)alphas with more than 2 decimals migrate to a percentage modifier with the same opacity (e.g.theme(colors.red.500/.12345)→text-red-500/[12.345%], nottext-red-500/[12.345])Canonicalization: Preserve inline
theme(…)alphas as an arbitrary percentage when a custom--opacity-*theme value would change the opacity (e.g.theme(colors.red.500/50%)→text-red-500/[50%]with--opacity-50: 10%)Ensure the
@propertyfallback isn't applied in Safari versions that no longer supportmargin-trim: inlineTreat viewport units like
dvminandsviand font-relative units likecapandrexas lengths in arbitrary values (e.g.text-[10dvmin]generatesfont-sizeinstead ofcolor)Write plugin logs to stderr in
tailwindcss canonicalizeso they don't end up in the results on stdoutExtract class shorthands on later lines when Pug text, comments, or quoted attribute values contain unbalanced brackets, or a quote that doesn't start a string (e.g.
input(pattern=/"/.source)) (#20547, #20572)Underline the correct occurrence of an unsupported data type in
--value(…)warningsCanonicalization: Prefer an existing candidate when collapsing utilities over another utility with the same default theme value (e.g.
text-foreground text-primary→text-primary, nottext-card-checked-border)Canonicalization: Don't collapse utilities into a utility that uses another theme variable with the same default value (e.g.
mt-card mb-card→my-card, notmy-4)Ensure
@tailwindcss/postcssrewrites relativeurl(…)s of stylesheets that are inlined before it runs (e.g.@imports in Vite) in optimized buildsDrop nested rules that put a combinator after a pseudo-element when using pseudo-element variants (e.g.
selection:*on a utility with a nested& > *rule)Don't generate CSS for arbitrary values with unbalanced parentheses or brackets (e.g.
w-[calc(1px]or[--x:a[b])Canonicalization: Prevent
collapse: truefrom taking exponentially longer when classes are linked through a utility that sets many properties (e.g.sr-only)Ensure
&is substituted inside:-moz-any(…)and:-webkit-any(…)in custom variants (e.g.@custom-variant firefox (:-moz-any(&));)Ensure the standalone macOS binaries have a valid code signature, so macOS 27 no longer kills them at launch
Ensure
@tailwindcss/turbopackand@tailwindcss/webpackrebuild when the input CSS changes (e.g.next devwith Turbopack no longer serves the CSS of the previous edit)Canonicalization: Don't drop a utility that sets a
--tw-*variable when an unrelated property has the same value (e.g.link mt-4no longer becomesmt-4whenlinksetsmargin-top: 16pxand--tw-translate-x: 16px)Decode single-digit hexadecimal escapes in theme variable and
@utilitynames as the CSS spec does (e.g.@theme { --color-\0: red; }no longer registers--color-0)Don't treat
!importantinside strings, comments orurl()in declaration values as the important flag (e.g.content: "a !important b")Parse a custom property at the end of the input when it has no trailing
;(e.g.--foo: baras the last declaration)Keep a declaration without a
;at the end of the CSS input (e.g.color: red)
4.3.3
31 Jul 2026
Notes older than 90 days are read on the Releases tab.
Dependency tracking · free for 3 projects
Know when your own dependencies move
This page watches @tailwindcss/turbopack. inlinr reads your package.json and keeps the same watch on every dependency you declare, then tells you only what needs you.
Advisories reach you
An email when a critical or high advisory affects a project, before the next install.
Upgrades checked first
Peer ranges, Node, ESM-only and types changes read before you bump.
Only what matters
Majors and breaking notes stay; patches and sibling bumps fold into one line.
Reading releases, release notes and advisories…
Registry facts last checked 3 Nov 2026. Releases and advisories last read 3 Nov 2026.