-
Notifications
You must be signed in to change notification settings - Fork 0
Update dependency tailwind-variants to v3 #334
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
package.json
Outdated
| "react-dom": "^19.0.0", | ||
| "server-only": "^0.0.1", | ||
| "tailwind-variants": "^0.3.1" | ||
| "tailwind-variants": "^3.1.1" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Bug: The upgrade of tailwind-variants requires tailwind-merge as a peer dependency, but it was not added to package.json, which will cause a runtime error.
(Severity: Critical 0.90 | Confidence: 0.95)
🔍 Detailed Analysis
The tailwind-variants package was upgraded to v3.1.1, which changed tailwind-merge from a direct dependency to a peer dependency. The code continues to import from tailwind-variants/transformer, the standard build that requires tailwind-merge for class name conflict resolution. However, tailwind-merge was not added to the package.json as a dependency. This will cause the application to fail at runtime with a module resolution error when withTV is called and attempts to import the missing tailwind-merge module.
💡 Suggested Fix
Add tailwind-merge as a dependency in package.json. For example: "tailwind-merge": ">=3.0.0". Alternatively, if conflict resolution is not needed, switch the import to use the lite build: import { withTV } from 'tailwind-variants/lite';.
🤖 Prompt for AI Agent
Fix this bug. In package.json at line 28: The `tailwind-variants` package was upgraded
to v3.1.1, which changed `tailwind-merge` from a direct dependency to a peer dependency.
The code continues to import from `tailwind-variants/transformer`, the standard build
that requires `tailwind-merge` for class name conflict resolution. However,
`tailwind-merge` was not added to the `package.json` as a dependency. This will cause
the application to fail at runtime with a module resolution error when `withTV` is
called and attempts to import the missing `tailwind-merge` module.
Did we get this right? 👍 / 👎 to inform future reviews.
89c9631 to
2747755
Compare
2747755 to
0b61a01
Compare
0b61a01 to
fbe6de4
Compare
fbe6de4 to
32b8d93
Compare
This PR contains the following updates:
^0.3.1->^3.2.2Release Notes
heroui-inc/tailwind-variants (tailwind-variants)
v3.2.2Compare Source
v3.2.1Compare Source
Bug Fixes
v3.2.0Compare Source
Bug Fixes
Features
3.1.1 (2025-09-08)
Bug Fixes
v3.1.1Compare Source
Bug Fixes
v3.1.0Compare Source
Features
v3.0.0Compare Source
Features
v2.1.0Compare Source
Features
2.0.1 (2025-07-28)
v2.0.1Compare Source
Features
2.0.1 (2025-07-28)
v2.0.0Compare Source
Features
2.0.1 (2025-07-28)
v1.0.0Compare Source
What's Changed
Breaking change
responsiveVariantsoption has been removed.withTvhas been removed.New Contributors
Full Changelog: heroui-inc/tailwind-variants@v0.3.1...v1.0.0
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.