tailwind-merge is a JavaScript utility function for merging Tailwind CSS utility classes without style conflicts. It helps combine class strings efficiently, removing or overriding conflicting Tailwind classes, and is typed for TypeScript use.
Project status
- The repository appears actively maintained, with multiple recent
v3.xupdates (latestv3.6.0dated 2026-05-10) and an upstream push on 2026-05-24. - The apparent update cadence is fairly steady, with
v3.5.0on 2026-02-18, followed closely byv3.4.1on 2026-02-15, and then the next major stepv3.6.0on 2026-05-10.
AI summary generated Today
Recent updates
v3.6.0
4 weeks agov3.6.0 updates tailwind-merge to support Tailwind CSS v4.3, including new class groups and parsing/merging behavior for named container queries that involve slashes in the full class name. It also adds type support for readonly array values and hardens GitHub Actions by removing git checkout in an internal CI/release comment workflow.
SecurityFeaturesv3.5.0
3 months agov3.5.0 primarily adds support for Tailwind CSS v4.2. The library updates its Tailwind class-group mapping and parsing logic to recognize new logical utilities, and adds corresponding test coverage. Additionally, the repository introduces a new GitHub workflow and local action for commenting released PRs and issues.
Featuresv3.4.1
3 months agov3.4.1 is described in the release notes as a small bug fix preventing arbitrary font-family and font-weight from merging. The actual code diff for this release is much larger, including internal refactors of class parsing, modifier sorting, config merging, and cache behavior. Several of these changes introduce API or behavior differences that are not covered by the release notes.
v2.6.1
4 months agov2.6.1 is a small bug fix release for tailwind-merge. The stated change ensures that arbitrary values involving the CSS `color-mix(...)` function are correctly detected/treated as colors during conflict resolution.
v3.4.0
7 months agov3.4.0 focuses on performance improvements for tailwind-merge (claimed to be over 10% faster), plus documentation and benchmarking updates. The release notes describe the existence of optimizations, but they do not detail several code-level refactors and type-level changes that could affect edge-case behavior or advanced TypeScript usage.
Featuresv3.3.1
12 months agov3.3.1 is a small bug fix release. It updates the class parsing logic so tailwind-merge correctly recognizes CSS `color-mix(...)` as a color function when it appears inside arbitrary values.
v3.3.0
5/11/2025v3.3.0 primarily adds Tailwind CSS v4.1.5 support. Concretely, the merge rules for height utilities were updated so that the new `lh`-based variants are recognized and merged correctly.
Featuresv3.2.0
4/6/2025v3.2.0 extends tailwind-merge to support Tailwind CSS v4.1. The code diff shows substantial updates to the default configuration and class group/type definitions to recognize new v4.1 utilities such as text-shadow, drop-shadow-color, mask utilities, and wrap modifiers. Several validator rules for parsing arbitrary values were also changed, which can alter merge/conflict behavior beyond what the release notes explicitly call out.
Featuresv3.1.0
3/31/2025tailwind-merge v3.1.0 adds support for Tailwind CSS v4.0.10 and includes a targeted fix for how `via-(length:*)` gradient classes are merged. It also updates the metrics-report GitHub action to avoid failing on pull requests from forks. Most code changes are centered around Tailwind theme parsing configuration and how gradient-related class groups are recognized.
Featuresv3.0.2
2/22/2025v3.0.2 is a patch release focused on correcting how tailwind-merge recognizes the `px` spacing token for some utility class groups. It also includes a documentation-only fix related to the default config comment placement. Despite the small release notes, the code changes include a broader refactor of the default spacing-related “scale” definitions, which can change class conflict resolution.