📦 (deps-dev) tailwind 🌬️ [skip ci] (major)

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
tailwind-merge	2.6.0 -> 3.0.1
tailwind-merge	^2.2.1 -> ^2.2.1 || ^3.0.0
tailwindcss (source)	3.4.17 -> 4.0.3

---

Release Notes

dcastil/tailwind-merge (tailwind-merge)

v3.0.1

Compare Source

Bug Fixes

• Update info about supported Tailwind CSS version in README by @​dcastil in b9c136d
• Update incorrect link in v3 changelog by @​dcastil in e22885e

Full Changelog: dcastil/tailwind-merge@v3.0.0...v3.0.1

Thanks to @​brandonmcconnell, @​manavm1990, @​langy, @​jamesreaco, @​roboflow, @​syntaxfm, @​getsentry, @​codecov and a private sponsor for sponsoring tailwind-merge! ❤️

v3.0.0

Compare Source

Tailwind CSS v4 is here and it's time to upgrade tailwind-merge to support it. tailwind-merge v3.0.0 is more accurate than ever and follows the Tailwind CSS spec more closely than in v2. That is thanks to Tailwind CSS v4 being more consistent than ever.

This release drops support for Tailwind CSS v3 and in turn adds support for Tailwind CSS v4. That means you should upgrade to Tailwind CSS v4 and tailwind-merge v3 together. All breaking changes are related to the Tailwind CSS v4 support.

Check out the migration guide and if you have any questions, feel free to create an issue.

Breaking Changes

• Dropping support for Tailwind CSS v3 in favor of support for Tailwind CSS v4 by @​dcastil in https://github.com/dcastil/tailwind-merge/pull/518
• Theme scales keys changed and now match Tailwind CSS v4 theme variable namespace exactly by @​dcastil in https://github.com/dcastil/tailwind-merge/pull/518
• isLength validator was removed and split into separate validators isNumber and isFraction by @​dcastil in https://github.com/dcastil/tailwind-merge/pull/518
• Prefix defined in config shouldn't include combining - character anymore by @​dcastil in https://github.com/dcastil/tailwind-merge/pull/518
• Tailwind CSS v3 prefix position in class not supported anymore in favor of Tailwind CSS v4 position by @​dcastil in https://github.com/dcastil/tailwind-merge/pull/518
• Custom separators are no longer supported by @​dcastil in https://github.com/dcastil/tailwind-merge/pull/518
• New mandatory orderSensitiveModifiers property in config when using createTailwindMerge by @​dcastil in https://github.com/dcastil/tailwind-merge/pull/518
• DefaultThemeGroupIds type union consists of different string literals than before by @​dcastil in https://github.com/dcastil/tailwind-merge/pull/518
• Classes removed in Tailwind CSS v4 are not supported by tailwind-merge anymore by @​dcastil in https://github.com/dcastil/tailwind-merge/pull/518

New Features

• Support for new important modifier position at the end of class by @​dcastil in https://github.com/dcastil/tailwind-merge/pull/518
• Support for arbitrary CSS variable syntax by @​dcastil in https://github.com/dcastil/tailwind-merge/pull/518
• There are a bunch of new validators used by tailwind-merge, primarily for new Tailwind CSS v4 features like arbitrary CSS variables by @​dcastil in https://github.com/dcastil/tailwind-merge/pull/518

Bug Fixes

• Previously some order-sensitive modifiers like before: were treated as not order-sensitive. This is now fixed by @​dcastil in https://github.com/dcastil/tailwind-merge/pull/518

Documentation

• Added section explaining order-sensitive modifiers to configuration docs by @​dcastil in https://github.com/dcastil/tailwind-merge/pull/518

Full Changelog: dcastil/tailwind-merge@v2.6.0...v3.0.0

Thanks to @​brandonmcconnell, @​manavm1990, @​langy, @​jamesreaco, @​roboflow, @​syntaxfm, @​getsentry, @​codecov and a private sponsor for sponsoring tailwind-merge! ❤️

tailwindlabs/tailwindcss (tailwindcss)

v4.0.3

Compare Source

Fixed

• Fix incorrect removal of @import url(); (#​16144)

v4.0.2

Compare Source

Fixed

• Only generate positive grid-cols-* and grid-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)

v4.0.1

Compare Source

Added

• Include :open pseudo-class in existing open variant (#​15349)

Fixed

• Remove invalid min-w/h-none utilities (#​15845)
• Discard CSS variable shorthand utilities that don't use valid CSS variables (#​15738)
• Ensure font-size utilities with none modifier have a line-height set e.g. text-sm/none (#​15921)
• Ensure font-size utilities with unknown modifier don't generate CSS (#​15921)
• Don’t suggest font weight utilities more than once (#​15857)
• Suggest container query variants (#​15857)
• Disable bare value suggestions when not using the --spacing variable (#​15857)
• Ensure suggested classes are properly sorted (#​15857)
• Don’t look at .gitignore files outside initialized repos (#​15941)
• Find utilities when using the Svelte class shorthand syntax across multiple lines (#​15974)
• Find utilities when using the Angular class shorthand syntax (#​15974)
• Find utilities when using functions inside arrays (#​15974)
• Ensure that @tailwindcss/browser does not pollute the global namespace (#​15978)
• Ensure that tailwind-merge is not scanned when using the Vite plugin (#​16005)
• Ensure CSS theme variables are available within shadow roots (#​15975)
• Fix crash when project lives in the / directory (#​15988)
• Ensure custom variants have a non-empty selector list (#​16009)
• Upgrade: Ensure JavaScript config files on different drives are correctly migrated (#​15927)
• Upgrade: Migrate leading-[1] to leading-none (#​16004)
• Upgrade: Do not migrate arbitrary leading utilities to bare values (#​16004)

v4.0.0

Compare Source

Added

• New high-performance engine — where full builds are up to 5x faster, and incremental builds are over 100x faster — and measured in microseconds.
• Designed for the modern web — built on cutting-edge CSS features like cascade layers, registered custom properties with @property, and color-mix().
• Simplified installation — fewer dependencies, zero configuration, and just a single line of code in your CSS file.
• First-party Vite plugin — tight integration for maximum performance and minimum configuration.
• Automatic content detection — all of your template files are discovered automatically, with no configuration required.
• Built-in import support — no additional tooling necessary to bundle multiple CSS files.
• CSS-first configuration — a reimagined developer experience where you customize and extend the framework directly in CSS instead of a JavaScript configuration file.
• CSS theme variables — all of your design tokens exposed as native CSS variables so you can access them anywhere.
• Dynamic utility values and variants — stop guessing what values exist in your spacing scale, or extending your configuration for things like basic data attributes.
• Modernized P3 color palette — a redesigned, more vivid color palette that takes full advantage of modern display technology.
• Container queries — first-class APIs for styling elements based on their container size, no plugins required.
• New 3D transform utilities — transform elements in 3D space directly in your HTML.
• Expanded gradient APIs — radial and conic gradients, interpolation modes, and more.
• @​starting-style support — a new variant you can use to create enter and exit transitions, without the need for JavaScript.
• not-* variant — style an element only when it doesn't match another variant, custom selector, or media or feature query.
• Even more new utilities and variants — including support for color-scheme, field-sizing, complex shadows, inert, and more.

Start using Tailwind CSS v4.0 today by installing it in a new project, or playing with it directly in the browser on Tailwind Play.

For existing projects, we've published a comprehensive upgrade guide and built an automated upgrade tool to get you on the latest version as quickly and painlessly as possible.

For a deep-dive into everything that's new, check out the announcement post.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---