tailwindcss
Advanced tools
Changelog
[4.0.0-alpha.31] - 2024-10-29
source(…)
function on @tailwind utilities
or @import "tailwindcss"
(#14820)source(none)
(#14820)@source
without needing to pass a complete glob (#14820)prettier-plugin-tailwindcss
to latest version during upgrade (#14808)config()
with no arguments in plugin API (#14799)Changelog
[4.0.0-alpha.30] - 2024-10-24
not-*
with all built-in media query and supports-*
variants (#14743)not-*
with custom variants containing at-rules (#14743)group-*
, peer-*
, and has-*
with custom variants containing multiple, non-nested style rules (#14743)<div v-if="!border" />
) (#14774)exports
in their package.json
are resolved correctly (#14775)url()
function are never unescaped (#14776)@import
statements for relative CSS files are actually migrated to use relative path syntax (#14769)m-[var(--spacing-1_5)]
instead of m-[var(--spacing-1\_5)]
) (#14778)layer(…)
on @import
is only removed when @utility
is present (#14783)Changelog
[4.0.0-alpha.29] - 2024-10-23
plugins
with options to CSS (#14700)corePlugins
options to be migrated to CSS (#14742)@import
statements for relative CSS files to use relative path syntax (e.g. ./file.css
) (#14755)max-w-screen-*
utilities to max-w-[var(…)]
(#14754)@variants
and @responsive
directives (#14748)@screen
directive (#14749)postcss
as a dependency of @tailwindcss/postcss
(#14750)theme()
function can reference CSS theme variables that contain special characters without escaping them (e.g. referencing --width-1\/2
as theme('width.1/2')
) (#14739)'1/2': 50%
to w-1/2
) (#14739)addUtilities
(#14747)?raw
and ?url
static asset query works when using the Vite plugin (#14716)flex-grow
to grow
and flex-shrink
to shrink
(#14721)1
(like theme(spacing.1)
) are correctly migrated to custom properties (#14724)from-*
, via-*
, and to-*
utilities (#14725)layer(utilities)
is removed from @import
to keep @utility
top-level (#14738)let foo = !border
to let foo = border!
) (#14737)Changelog
[4.0.0-alpha.28] - 2024-10-17
theme(…)
calls to var(…)
or to the modern theme(…)
syntax (#14664, #14695)theme
object (#14675)theme
values defined outside of extend
in JS configuration files overwrite all existing values for that namespace (#14672)screens
config (#14691)Changelog
[4.0.0-alpha.27] - 2024-10-15
tailwindcss/colors.js
, tailwindcss/defaultTheme.js
, and tailwindcss/plugin.js
exports (#14595)keyframes
in JS config file themes (#14594)color
parameter in JS theme configuration callbacks (#14651)theme()
function (#14659)@config "…"
when a tailwind.config.{js,ts,…}
is detected (#14635)@media screen(…)
when running codemods (#14603)aria-*
, data-*
, and supports-*
variants from arbitrary values to bare values (#14644)!important
when stringifying CSS (#14611)display: none
on elements that use hidden="until-found"
(#14631)theme()
function resolves to the right value in some compatibility situations (#14614)matchUtilities
(#14589)addComponents
and matchComponents
(#14590)boxShadow
and animation
theme keys in JS config files are accessible under --shadow-*
and --animate-*
using the theme()
function (#14642)theme()
function with the legacy dot notation syntax (#14642)var(…)
can be used as the opacity value inside the theme([path] / [modifier])
function (#14653)font-stretch
utilities only accepts positive integer bare values (#14670)