Releases: tailwindlabs/tailwindcss
Releases · tailwindlabs/tailwindcss
v4.0.15
Fixed
- Fix incorrect angle in
-bg-conic-*
utilities (#17174) - Fix
border-[12px_4px]
being interpreted as aborder-color
instead of aborder-width
(#17248) - Work around a crash in Safari 16.4 and 16.5 when using the default Preflight styles (#17306)
- Pre-process
<template lang="…">
in Vue files (#17252) - Ensure that all CSS variables used by Preflight are prefixed (#17036)
- Prevent segfault when loaded in a worker thread on Linux (#17276)
- Ensure multiple
--value(…)
or--modifier(…)
calls don't delete subsequent declarations (#17273) - Fix class extraction followed by
(
in Slim (#17278) - Export
PluginUtils
fromtailwindcss/plugin
for compatibility with v3 (#17299) - Remove redundant
line-height: initial
from Preflight (#15212) - Increase Standalone hardware compatibility on macOS x64 builds (#17267)
- Ensure that the CSS file rebuilds if a new CSS variable is used from templates (#17301)
Changed
- The
--theme(…)
function now returns CSS variables from your theme variables unless used inside positions where CSS variables are invalid (e.g. inside@media
queries) (#17036)
v4.0.14
v4.0.13
Fixed
- Fix Haml pre-processing (#17051)
- Ensure
.node
and.wasm
files are not scanned for utilities (#17123) - Improve performance when scanning JSON files (#17125)
- Fix extracting candidates containing dots in Haml, Pug, and Slim pre processors (#17094, #17085, #17113)
- Don't create invalid CSS when encountering a link wrapped in square brackets (#17129)
v4.0.12
Fixed
- Vite: Fix
url(…)
rebasing in transitively imported CSS files (#16965) - PostCSS: Rebase
url(…)
s in imported CSS files (#16965) - Ensure utilities are sorted based on their actual property order (#16995)
- Ensure strings in Pug and Slim templates are handled correctly (#17000)
- Ensure classes between
}
and{
are properly extracted (#17001) - Fix
razor
/cshtml
pre-processing (#17027) - Ensure extracting candidates from JS embedded in a PHP string works as expected (#17031)
v4.0.11
Fixed
- Ensure classes containing
--
are extracted correctly (#16972) - Ensure classes containing numbers followed by dash or underscore are extracted correctly (#16980)
- Ensure arbitrary container queries are extracted correctly (#16984)
- Ensure classes ending in
[
are extracted in Slim templating language (#16985) - Ensure arbitrary variables with data types are extracted correctly (#16986)
v4.0.10
Added
- Add
col-<number>
androw-<number>
utilities forgrid-column
andgrid-row
(#15183)
Fixed
- Ensure
not-*
does not remove:is(…)
from variants (#16825) - Ensure
@keyframes
are correctly emitted when using a prefix (#16850) - Don't swallow
@utility
declarations when@apply
is used in nested rules (#16940) - Ensure
outline-hidden
behaves likeoutline-none
outside of forced colors mode (#16943) - Allow
!important
on CSS variables again (#16873) - Vite: Do not crash when encountering an
.svg
file with#
or?
in the filename (#16957) - Ensure utilities are properly detected within square brackets (#16306)
- Ensure utilities are properly detected using Angular's conditional class binding syntax (#16306)
- Ensure utilities starting with numbers are properly extracted from Slim templates (#16306)
- Discard arbitrary property candidates that have guaranteed-invalid property names (#16306)
Changed
v4.0.9
Fixed
- Make JS APIs available to plugins and configs in the Standalone CLI (#15934)
- Vite: Don't crash when importing a virtual module from JavaScript that ends in
.css
(#16780) - Fix an issue where
@reference "…"
would sometimes omit keyframe animations (#16774) - Ensure
z-*!
utilities are properly marked as!important
(#16795) - Read UTF-8 CSS files that start with a byte-order mark (BOM) (#16800)
- Ensure nested functions in selectors used with JavaScript plugins are not truncated (#16802)
Changed
- Emit variable fallbacks when using
@reference "…"
instead of duplicate CSS variable declarations (#16774)
v4.0.8
Added
- Allow
@import
withtheme(…)
options for stylesheets that contain more than just@theme
rules (#16514)
Fixed
- Don't add
!important
to CSS variable declarations when using the important modifier (#16668) - Vite: Ignore files and directories specified in your
.gitignore
file when using automatic source detection(#16631) - Vite: Don't rely on the module graph for detecting candidates to ensure setups with multiple Vite builds work as expected (#16631)
- Vite: Ensure Astro production builds always contain classes used in client-only components (#16631)
- Vite: Always scan raw file contents for utility classes before any other transforms have been applied to ensure utility classes are scanned without any additional escaping (#16631)
- Ensure utilities with more declarations are always sorted before utilities with fewer declarations when utilities only define CSS variables (#16715)
- Only include
translate-z-px
utilities once in compiled CSS (#16718)
Changed
v4.0.7
Fixed
- Export
tailwindcss/lib/util/flattenColorPalette.js
for backward compatibility (#16411) - Fix sorting of numeric utility suggestions when they have different magnitudes (#16414)
- Show suggestions for fractions in IntelliSense (#16353)
- Don’t replace
_
in suggested theme keys (#16433) - Ensure
--default-outline-width
can be used to change theoutline-width
value of theoutline
utility (#16469) - Ensure drop shadow utilities don't inherit unexpectedly (#16471)
- Export config and plugin types from
tailwindcss/plugin
for backward compatibility (#16505) - Ensure JavaScript plugins that emit nested rules referencing the utility name work as expected (#16539)
- Statically link Visual Studio redistributables in
@tailwindcss/oxide
Windows builds (#16602) - Ensure that Next.js splat routes are scanned for classes (#16457)
- Pin exact version of
tailwindcss
in@tailwindcss/*
packages (#16623) - Upgrade: Report errors when updating dependencies (#16504)
- Upgrade: Ensure a
darkMode
JS config setting with block syntax converts to use@slot
(#16507) - Upgrade: Ensure the latest version of
tailwindcss
and@tailwindcss/postcss
are installed when upgrading (#16620)