Tailwind Merge Versions Save

Merge Tailwind CSS classes without style conflicts

v2.3.0

1 month ago

New Features

Documentation

Full Changelog: https://github.com/dcastil/tailwind-merge/compare/v2.2.2...v2.3.0

Thanks to @brandonmcconnell, @manavm1990, @langy and @jamesreaco for sponsoring tailwind-merge! ❤️

v2.2.2

3 months ago

Bug Fixes

Documentation

Full Changelog: https://github.com/dcastil/tailwind-merge/compare/v2.2.1...v2.2.2

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

v2.2.1

4 months ago

Bug Fixes

Full Changelog: https://github.com/dcastil/tailwind-merge/compare/v2.2.0...v2.2.1

Thanks to @brandonmcconnell, @manavm1990 and @langy for sponsoring tailwind-merge! ❤️

v2.2.0

5 months ago

New Features

Full Changelog: https://github.com/dcastil/tailwind-merge/compare/v2.1.0...v2.2.0

Thanks to @brandonmcconnell, @manavm1990, @ErwinAI and @langy for sponsoring tailwind-merge! ❤️

v2.1.0

6 months ago

New Features

Bug Fixes

Documentation

Full Changelog: https://github.com/dcastil/tailwind-merge/compare/v2.0.0...v2.1.0

Thanks to @brandonmcconnell, @manavm1990, @ErwinAI and @langy for sponsoring tailwind-merge! ❤️

v2.0.0

7 months ago

The tailwind-merge v2 release has been sitting here almost finished for 2 months already. But the timing was never quite right, especially thinking about the increased support needed after the release. In the meantime, the product of the company I work at launched in public beta and I married. Thank you for your patience.

This release focuses on making it easier to configure the library for new users. Check out the migration guide and if you have any questions, feel free to create an issue.

Breaking Changes

New Features

Bug Fixes

Documentation

Full Changelog: https://github.com/dcastil/tailwind-merge/compare/v1.14.0...v2.0.0

Thanks to @quezlatch, @brandonmcconnell, @manavm1990 and @ErwinAI for sponsoring tailwind-merge! ❤️

v1.14.0

11 months ago

New Features

  • Improve support for arbitrary values by @dcastil in https://github.com/dcastil/tailwind-merge/pull/263
    • Previously, tailwind-merge checked the content of the arbitrary value portion of a class in most cases to understand whether the type of the arbitrary value is correct (e.g. it checked for number followed by length unit for the length type). That lead to the issue that a class like mt-[calc(theme(fontSize.4xl)/1.125)] would not be recognized correctly because no length unit is present in the arbitrary value.
    • I changed the check of the arbitrary value to also pass when a calc(), min(), max() and clamp() function is used in the arbitrary value.
    • In ambiguous cases, you can use data type labels to mark the type of a class. Read more
    • Moreover, I removed the check where the type of the arbitrary value is unambiguous. In the class mt-[…] the arbitrary value can only be a length, so I don't check for it. A consequence of this is that if you use non-Tailwind classes like mt-[this-is-totally-not-tailwind], tailwind-merge will recognize it as a Tailwind class from now on. Please don't use classes that look like Tailwind classes with arbitrary value but aren't Tailwind classes with tailwind-merge (in default config) to prevent incorrect merging behavior.

Bug Fixes

Documentation

Full Changelog: https://github.com/dcastil/tailwind-merge/compare/v1.13.2...v1.14.0

v1.13.2

1 year ago

Bug Fixes

Documentation

Full Changelog: https://github.com/dcastil/tailwind-merge/compare/v1.13.1...v1.13.2

Thanks to @bluetch for sponsoring tailwind-merge! ❤️

v1.13.1

1 year ago

Bug Fixes

Full Changelog: https://github.com/dcastil/tailwind-merge/compare/v1.13.0...v1.13.1

v1.13.0

1 year ago

This release focuses on improvements to the docs.

Bug Fixes

Documentation

Other

Full Changelog: https://github.com/dcastil/tailwind-merge/compare/v1.12.0...v1.13.0