npm tailwind-merge 1.13.0
v1.13.0

latest releases: 3.0.1-dev.6a90675ee3532f1e8b3c6e00ae120c295177bbf2, 3.0.1-dev.f3cdb9523f5f5a9bcf40e12e95846afda5f534a5, 3.0.1-dev.e80f256fb5654a2812ad9c326ec67370b4c7c18c...
20 months ago

This release focuses on improvements to the docs.

Bug Fixes

Documentation

  • Add intro video from Simon Vrachliotis to docs by @dcastil in #239
    • @simonswiss made an intro video to tailwind-merge which I added to the docs. Check it out here!
  • Add docs about when to use tailwind-merge by @dcastil in #230
    • I added a new page to the docs about when and how to use tailwind-merge which should help you to decide whether you should use it and what alternative approaches exist.
  • Make it clearer in docs that tailwind-merge supports composition of class strings by @dcastil in #229

Other

  • Add npm package provenance by @dcastil in #219
    • GitHub introduced a new security feature to verify which source commit and build file were used for a specific npm package version. tailwind-merge now publishes provenance signatures alongside all releases on npm. Read more on the GitHub blog.

Full Changelog: v1.12.0...v1.13.0

Don't miss a new tailwind-merge release

NewReleases is sending notifications on new releases.