Releases: tailwindlabs/tailwindcss
Releases · tailwindlabs/tailwindcss
v4.0.0-beta.10
Added
- Add support for using
@variant
to use variants in your CSS (#15663) - Include
outline-color
when transitioning colors (#15690)
Fixed
- Add missing
main
andbrowser
fields for@tailwindcss/browser
(#15594) - Support escaping
*
in theme namespace syntax (e.g.:--color-\*: initial;
) (#15603) - Respect
@theme
options when resolving values in custom functional utilities (#15623) - Discard invalid variants (e.g.
data-checked-[selected=1]:*
) (#15629) - Ensure
-outline-offset-*
utilities are suggested in IntelliSense (#15646) - Write to
stdout
when--output
is set to-
or omitted with@tailwindcss/cli
(#15656) - Prevent
not-*
from being used with variants that have multiple sibling rules (#15689) - Upgrade (experimental): Pretty print
--spacing(…)
to prevent ambiguity (#15596)
Changed
v4.0.0-beta.9
Added
- Add
@tailwindcss/browser
package to run Tailwind CSS in the browser (#15558) - Add
@reference "…"
API as a replacement for the previous@import "…" reference
option (#15565) - Add support for defining functional utilities in CSS (#15455)
- Add new
--spacing(…)
,--alpha(…)
, and--theme(…)
CSS functions (#15572) - Add musl-based Linux builds of the standalone CLI (#15567)
- Improve performance of internal AST manipulations (#15529)
Fixed
- Use the correct property value for
place-content-between
,place-content-around
, andplace-content-evenly
utilities (#15440) - Don’t detect arbitrary properties when preceded by an escape (#15456)
- Fix incorrectly named
bg-round
andbg-space
utilities tobg-repeat-round
tobg-repeat-space
(#15462) - Fix
inset-shadow-*
suggestions in IntelliSense (#15471) - Only compile arbitrary values ending in
]
(#15503) - Ensure
@apply
rules are processed in the correct order (#15542) - Allow negative utility names in
@utility
(#15573) - Remove all
@keyframes
contributed by JavaScript plugins when using@reference
imports (#15581) - Upgrade (experimental): Do not extract class names from functions (e.g.
shadow
infilter: 'drop-shadow(…)'
) (#15566) - Upgrade (experimental): Migrate
theme(spacing.2)
to--spacing(2)
(#15579) - Upgrade (experimental): Migrate
theme(…)
to--theme(…)
(#15579)
Changed
v4.0.0-beta.8
Fixed
- Ensure
Symbol.dispose
andSymbol.asyncDispose
are polyfilled (#15404)
v3.4.17
v4.0.0-beta.7
Added
- Export
tailwindcss/lib/util/flattenColorPalette
for backward compatibility (#15318) - Improve debug logs to get better insights (#15303)
Fixed
- Fix dependency related warnings when using
@tailwindcss/postcss
on Windows (#15321) - Skip creating a compiler for CSS files that should not be processed (#15340)
- Fix missing
shadow-none
suggestion in IntelliSense (#15342) - Optimize AST before printing for IntelliSense (#15347)
- Generate vendor prefixes for Chrome 111+ (e.g.
-webkit-background-clip: text
) (#15389)
Changed
v4.0.0-beta.6
Fixed
- Ensure
@import "…" reference
never generates utilities (#15307)
v4.0.0-beta.5
Added
- Parallelize parsing of individual source files (#15270)
- Add new
@import "…" reference
option for importing Tailwind CSS configuration details into another CSS entry point without duplicating CSS (#15228) - Improve performance of
@tailwindcss/postcss
by translating between internal data structures and PostCSS nodes directly without additional parsing or stringification (#15297)
Fixed
- Ensure absolute URLs inside imported CSS files are not rebased when using
@tailwindcss/vite
(#15275) - Fix issues with dev servers using Svelte 5 with
@tailwindcss/vite
(#15274) - Support installing
@tailwindcss/vite
in Vite 6 projects (#15274) - Fix resolution of imported CSS files in SSR builds with
@tailwindcss/vite
(#15279) - Ensure other plugins can run after
@tailwindcss/postcss
(#15273) - Rebase URLs inside imported CSS files when using Vite with the
@tailwindcss/postcss
extension (#15273) - Fix missing font family suggestions in IntelliSense (#15288)
- Fix missing
@container
suggestion in IntelliSense (#15288)
v3.4.16
v4.0.0-beta.4
Fixed
- Don't scan source files for utilities unless
@tailwind utilities
is present in the CSS in@tailwindcss/postcss
and@tailwindcss/vite
(#15226) - Skip reserializing CSS files that don't use Tailwind features in
@tailwindcss/postcss
and@tailwindcss/vite
(#15226) - Upgrade (experimental): Do not migrate the
overflow-clip
utility (#15244) - Upgrade (experimental): Rename
backdrop-blur
tobackdrop-blur-sm
andbackdrop-blur-sm
tobackdrop-blur-xs
(#15242)
v4.0.0-beta.3
Fixed
- Ensure any necessary vendor prefixes are generated for iOS Safari, Firefox, and Chrome (#15166)
- Ensure
.group
and.peer
are prefixed when using theprefix(…)
option (#15174) - Ensure 3D transforms render correctly in Safari (#15179)
- Ensure
--spacing-*
variables take precedence over--container-*
variables (#15180) - Fix scanning classes delimited by tab characters (#15169)
- Ensure opacity modifiers and semi-transparent gradients render correctly by default in Safari (#15201)
- Fix element size thrashing when transitioning gradients on elements with a defined font-size in Safari (#15216)
- Ensure
translate-*
utilities work with arbitrary values that usecalc(…)
(#15215) - Ensure gradient stop position utilities work with arbitrary values that use
calc(…)
(#15215) - Ensure Node addons are packaged correctly with Windows ARM builds (#15171)
- Ensure the Vite plugin resolves CSS and JS files according to the configured resolver conditions ([#15173])(#15173)
- Upgrade (experimental): Migrate prefixes for
.group
and.peer
classes (#15208)
Changed
- Interpolate gradients using OKLAB instead of OKLCH by default (#15201)
- Error when
layer(…)
in@import
is not first in the list of functions/conditions (#15109) - Use unitless line-height values for font-size variables in default theme (#15216)
- Don't register custom properties with explicit types unless those custom properties need to be animateable (#15215)