Bump tailwindcss from 3.4.10 to 4.0.9
Created by: dependabot[bot]
Bumps tailwindcss from 3.4.10 to 4.0.9.
Release notes
Sourced from tailwindcss's releases.
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)
... (truncated)
Changelog
Sourced from tailwindcss's changelog.
[4.0.9] - 2025-02-25
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)[4.0.8] - 2025-02-21
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
[4.0.7] - 2025-02-18
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)
... (truncated)
Commits
-
85d7375
Prepare v4.0.9 release (#16804) -
b56f12e
Ensure nested functions in selectors used with JavaScript plugins are not tru... -
294952f
Handle BOM (#16800) -
ef57e6e
Fixz-*!
utilities (#16795) -
b389483
Make@reference
emit variable fallbacks instead of CSS variable declaration... -
751eb74
Addinverted-colors
variant (#11693) -
62d3e74
Addwrap-anywhere
utility (#12128) -
419b3dc
Prepare v4.0.8 release (#16713) -
b47b6d2
Remove doubletranslate-z-px
values (#16718) -
113142a
Use amount of properties when sorting (#16715) - Additional commits viewable in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase
.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
-
@dependabot rebase
will rebase this PR -
@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it -
@dependabot merge
will merge this PR after your CI passes on it -
@dependabot squash and merge
will squash and merge this PR after your CI passes on it -
@dependabot cancel merge
will cancel a previously requested merge and block automerging -
@dependabot reopen
will reopen this PR if it is closed -
@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually -
@dependabot show <dependency name> ignore conditions
will show all of the ignore conditions of the specified dependency -
@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)