Releases: tailwindlabs/tailwindcss
Releases · tailwindlabs/tailwindcss
v4.1.10
v4.1.9
Fixed
- Correctly parse custom properties with strings containing semicolons (#18251)
- Upgrade: Migrate arbitrary modifiers without percentage signs to bare values (e.g.
/[0.16]
→/16
) (#18184) - Upgrade: Migrate CSS variable shorthands where fallback value contains function call (#18184)
- Upgrade: Migrate negative arbitrary values to negative bare values (e.g.
mb-[-32rem]
→-mb-128
) (#18212) - Upgrade: Do not migrate
blur
inwire:model.blur
(#18216) - Don't add spaces around CSS dashed idents when formatting math expressions (#18220)
v4.1.8
Added
- Improve error messages when
@apply
fails (#18059)
Fixed
- Upgrade: Do not migrate declarations that look like candidates in
<style>
blocks (#18057, 18068) - Upgrade: Don't error when looking for
tailwindcss
in pnpm monorepos (#18065) - Upgrade: Don't error when updating dependencies in pnpm monorepos (#18065)
- Upgrade: Migrate deprecated
order-none
toorder-0
(#18126) - Support Leptos
class:
attributes when extracting classes (#18093) - Fix "Cannot read properties of undefined" crash on malformed arbitrary value (#18133)
- Upgrade: Migrate
-mt-[0px]
tomt-[0px]
instead of the other way around (#18154) - Fix Haml pre-processing crash when there is no
\n
at the end of the file (#18155) - Ignore
.pnpm-store
folders by default (can be overridden by@source …
rules) (#18163) - Fix PostCSS crash when calling
toJSON()
(#18083)
v4.1.7
Added
- Upgrade: Migrate bare values to named values (#18000)
- Upgrade: Added cache to improve template migration performance (#18025)
Fixed
- Allow
_
before numbers during candidate extraction (#17961) - Prevent duplicate suggestions when using
@theme
and@utility
together (#17675) - Ensure that media queries within
::before
and::after
pseudo selectors create valid CSS rules in production builds (#17979) - Ensure that the standalone CLI does not leave temporary files behind (#17981)
- Ensure
-rotate-*
utilities properly negate arbitrary values (#18014) - Ignore custom variants using
:merge(…)
selectors in legacy JS plugins (#18020) - Ensure classes containing
.
are properly extracted from Clojure files (#18038) - Upgrade: Fix error when using
@import … source(…)
(#17963) - Upgrade: Change casing of utilities with named values to kebab-case to match updated theme variables (#18017)
- Upgrade: Don't migrate strings that match utility names in Vue attribute bindings other than
class
(#18025)
v4.1.6
Added
- Upgrade: Automatically convert arbitrary values to named values when possible (e.g.
h-[1lh]
toh-lh
) (#17831, #17854) - Upgrade: Update dependencies in parallel for improved performance (#17898)
- Add detailed logging about
@source
directives, discovered files and scanned files when usingDEBUG=*
(#17906, #17952) - Add support for generating source maps in development (#17775)
Fixed
- Ensure negative arbitrary
scale
values generate negative values (#17831) - Fix HAML extraction with embedded Ruby (#17846)
- Don't scan files for utilities when using
@reference
(#17836) - Fix incorrectly replacing
_
withbg-red-500/(--my_opacity)
(#17889) - Don't scan
.log
files for classes by default (#17906) - Ensure that custom utilities applying other custom utilities don't swallow nested
@apply
rules (#17925) - Download platform specific package if
optionalDependencies
are skipped (#17929)
v4.1.5
Added
- Support using
@tailwindcss/upgrade
to upgrade between versions of v4.* (#17717) - Add
h-lh
/min-h-lh
/max-h-lh
utilities (#17790) - Transition
display
,visibility
,content-visibility
,overlay
, andpointer-events
when usingtransition
to simplify@starting-style
usage (#17812)
Fixed
- Don't scan
.geojson
or.db
files for classes by default (#17700, #17711) - Hide default shadow suggestions when missing default shadow theme keys (#17743)
- Replace
_
with.
in theme suggestions for@utility
if surrounded by digits (#17733) - Skip
color-mix(…)
when opacity is100%
(#17815) - PostCSS: Ensure that errors in imported stylesheets are recoverable (#17754)
- Upgrade: Bump all Tailwind CSS related dependencies during upgrade (#17763)
- Upgrade: Don't add
-
to variants starting with@
(#17814) - Upgrade: Don't format stylesheets that didn't change when upgrading (#17824)
v4.1.4
Added
- Add experimental
@tailwindcss/oxide-wasm32-wasi
target for running Tailwind in browser environments like StackBlitz (#17558)
Fixed
- Ensure
color-mix(…)
polyfills do not cause used CSS variables to be removed (#17555) - Ensure
color-mix(…)
polyfills create fallbacks for theme variables that reference other theme variables (#17562) - Fix brace expansion in declining ranges like
{10..0..5}
and{0..10..-5}
(#17591) - Work around a Chrome rendering bug when using the
skew-*
utilities (#17627) - Ensure container query variant names can contain hyphens (#17628)
- Ensure
shadow-inherit
,inset-shadow-inherit
,drop-shadow-inherit
, andtext-shadow-inherit
inherit the shadow color (#17647) - Ensure compatibility with array tuples used in
fontSize
JS theme keys (#17630) - Ensure folders with binary file extensions in their names are scanned for utilities (#17595)
- Upgrade: Convert
fontSize
array tuple syntax to CSS theme variables (#17630)
v4.1.3
v4.1.2
Fixed
- Don't rely on the presence of
@layer base
to polyfill@property
(#17506) - Support setting multiple inset shadows as arbitrary values (#17523)
- Fix
drop-shadow-*
utilities that are defined with multiple shadows (#17515) - PostCSS: Fix race condition when two changes are queued concurrently (#17514)
- PostCSS: Ensure files containing
@tailwind utilities
are processed (#17514) - Ensure the
color-mix(…)
polyfill creates fallbacks even when using colors that cannot be statically analyzed (#17513) - Fix slow incremental builds with
@tailwindcss/vite
and@tailwindcss/postscss
(especially on Windows) (#17511) - Vite: Fix missing CSS file in Qwik setups (#17533)