Releases: tailwindlabs/tailwindcss
Releases · tailwindlabs/tailwindcss
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)
v4.0.6
v4.0.5
v4.0.4
Fixed
- Fix a crash when setting JS theme values to
null
(#16210) - Ensure escaped underscores in CSS variables in arbitrary values are properly unescaped (#16206)
- Ensure that the
containers
JS theme key is added to the--container-*
namespace (#16169) - Ensure theme
@keyframes
are generated even if an--animation-*
variable spans multiple lines (#16237) - Vite: Skip parsing stylesheets with the
?commonjs-proxy
flag (#16238) - Fix
order-first
andorder-last
for Firefox (#16266) - Fix support for older instruction sets on Linux x64 builds of the standalone CLI (#16244)
- Ensure
NODE_PATH
is respected when resolving JavaScript and CSS files (#16274) - Ensure Node addons are packaged correctly with FreeBSD builds (#16277)
- Fix an issue where
@variant
inside a referenced stylesheet could cause a stack overflow (#16300)
v4.0.3
v4.0.2
Fixed
- Only generate positive
grid-cols-*
andgrid-rows-*
utilities (#16020) - Ensure escaped theme variables are handled correctly (#16064)
- Ensure we process Tailwind CSS features when only using
@reference
or@variant
(#16057) - Refactor gradient implementation to work around prettier/prettier#17058 (#16072)
- Vite: Ensure hot-reloading works with SolidStart setups (#16052)
- Vite: Fix a crash when starting the development server in SolidStart setups (#16052)
- Vite: Don't rebase URLs that appear to be aliases (#16078)
- Vite: Transform
<style>
blocks in HTML files (#16069) - Prevent camel-casing CSS custom properties added by JavaScript plugins (#16103)
- Do not emit
@keyframes
in@theme reference
(#16120) - Discard invalid declarations when parsing CSS (#16093)
- Do not emit empty CSS rules and at-rules (#16121)
- Handle
@variant
when at the top-level of a stylesheet (#16129)