npm / tailwind-merge
tailwind-merge
What changed in tailwind-merge 2 to 3, from its official release notes, upgrade guides and advisories. Sources checked 2026-10-17.
2 new APIs and options1 performance3 behavior and defaults11 fixes and other
See which of these apply to your code, ranked, in your agent:
npx @unstale/cli inittailwind-merge 316 changes
New APIs and options 2
Theme getters now expose the referenced theme key so tooling can identify the theme scale without calling the getter.
Adds a config option for Tailwind utilities where a slash is part of the full class name, such as named container queries.
Performance 1
Performance optimizations make tailwind-merge more than 10% faster.
Behavior and default changes 3
Adds support for readonly array values in the technology's accepted inputs.
Adds support for Tailwind CSS v4.3 utilities, including utilities whose full class name contains a slash.
Adds support for Tailwind CSS v4.2, allowing tailwind-merge to handle its class names and utilities.
Fixes and other changes 10
Bare bg-conic now merges correctly with other background image classes.
Arbitrary values using color() are now classified as colors instead of lengths.
columns-auto now conflicts correctly with other columns classes.
Container sizes such as inline-2xl now merge correctly.
leading-none is no longer removed when the leading theme scale is overridden.
Arbitrary values using light-dark() are now classified as colors instead of lengths.
max-h-none is now included in the max-h class group.
Axis shorthand px now overrides logical sides such as ps correctly.
Deprecated shadow-inner is now classified as a shadow instead of a shadow color.
Prevents arbitrary font-family and font-weight values from merging incorrectly.
tailwind-merge 21 changes
Fixes and other changes 1
Arbitrary values using color-mix are now detected as colors by tailwind-merge.