Bump tailwind-merge from 1.14.0 to 2.0.0 in /frontend

[dependabot]

Bumps tailwind-merge from 1.14.0 to 2.0.0.

Release notes

Sourced from tailwind-merge's releases.

v2.0.0

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

• Fix background-image and background-position being merged incorrectly by @​dcastil in dcastil/tailwind-merge#300
  • Values for background-position and background-size can look very similar and Tailwind CSS uses the same bg- prefix for both groups. This results in some limitations for tailwind-merge. If you use background position or background size with arbitrary values, please read this section about how to use them.
• Make types of available keys more strict and configurable through generics by @​kachkaev in dcastil/tailwind-merge#279
• Make it possible to override elements with extendTailwindMerge by @​dcastil in dcastil/tailwind-merge#294
• Separate validators better by @​dcastil in dcastil/tailwind-merge#292
• Make conflictingClassGroupModifiers in config non-optional by @​dcastil in dcastil/tailwind-merge#291
• Move separator to config by @​dcastil in dcastil/tailwind-merge#290
• Remove module field from package.json by @​dcastil in dcastil/tailwind-merge#289
• Remove deprecated exports by @​dcastil in dcastil/tailwind-merge#288
• Transpile lib to more modern JS by @​dcastil in dcastil/tailwind-merge#287

New Features

• Make types of available keys more strict and configurable through generics by @​kachkaev in dcastil/tailwind-merge#279
• Make it possible to override elements with extendTailwindMerge by @​dcastil in dcastil/tailwind-merge#294
• Separate validators better by @​dcastil in dcastil/tailwind-merge#292
• Make conflictingClassGroupModifiers in config non-optional by @​dcastil in dcastil/tailwind-merge#291
• Move separator to config by @​dcastil in dcastil/tailwind-merge#290
• Remove module field from package.json by @​dcastil in dcastil/tailwind-merge#289
• Remove deprecated exports by @​dcastil in dcastil/tailwind-merge#288
• Transpile lib to more modern JS by @​dcastil in dcastil/tailwind-merge#287
• Add ES5 bundle by @​dcastil in dcastil/tailwind-merge#286

Bug Fixes

• Fix touch action classes overriding each other incorrectly by @​dcastil in dcastil/tailwind-merge#313
• Fix background-image and background-position being merged incorrectly by @​dcastil in dcastil/tailwind-merge#300
• Fix number validators accidentally returning true for empty strings by @​dcastil in dcastil/tailwind-merge#295
• Rename lazy-initializaton.test.ts to lazy-initialization.test.ts by @​CrutchTheClutch in dcastil/tailwind-merge#284

Documentation

• Explain limitations of arbitrary values in bg-size and bg-position class groups in docs by @​dcastil in dcastil/tailwind-merge#328

Full Changelog: dcastil/tailwind-merge@v1.14.0...v2.0.0

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

Commits

• 1b6ebb5 v2.0.0
• f3201af add v2 changelog
• e7c8c8a Merge pull request #329 from dcastil/docs/add-docs-for-stricter-extendtailwin...
• 4a08892 add docs for TypeScript types of extendTailwindMerge
• a6f27b3 Merge pull request #328 from dcastil/docs/301/explain-limitations-of-bg-size-...
• 661e855 add limitations to docs
• a962428 Merge pull request #324 from dcastil/dependabot/npm_and_yarn/babel/traverse-7...
• 360b9df Bump @​babel/traverse from 7.21.5 to 7.23.2
• 772ffb9 Merge pull request #318 from dcastil/renovate/actions-checkout-4.x
• 472f0ca Merge pull request #319 from dcastil/renovate/size-limit-preset-small-lib-9.x
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
neosync-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Oct 31, 2023 9:40pm

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.