refactor(*): migrate deprecated Tailwind v3 utility classes to v4#1034
Draft
sukvvon wants to merge 4 commits into
Draft
refactor(*): migrate deprecated Tailwind v3 utility classes to v4#1034sukvvon wants to merge 4 commits into
sukvvon wants to merge 4 commits into
Conversation
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
tanstack-com | 6670e67 | Commit Preview URL Branch Preview URL |
Jul 07 2026, 12:53 PM |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This project uses Tailwind CSS v4 (
tailwindcss@^4.2.2,@tailwindcss/vite), but several v3-era utility classes that were removed or renamed in v4 remained in the codebase. This PR migrates them and removes a stray@themeblock that produced a build warning.The changes are split into four logical commits.
Changes
1.
fix(admin/roles):bg-opacity-50→bg-black/50(1 occurrence)bg-opacity-*was removed in v4. The class was no longer generated, so the modal backdrop lost its opacity. Replaced with the slash opacity modifier.src/routes/admin/roles.$roleId.tsx2.
refactor(*):flex-shrink-0→shrink-0(33 occurrences, 16 files)flex-shrink-*was removed in v4 in favor ofshrink-*.3.
refactor(*):bg-gradient-to-*→bg-linear-to-*(60 occurrences, 25 files)bg-gradient-*was renamed tobg-linear-*in v4 (to distinguish it from the new radial/conic gradient utilities).4.
fix(styles/shop): remove@theme inlinefromshop.csssrc/styles/shop.cssis injected as a plain<link>stylesheet (imported with?url), so it never passes through the Tailwind pipeline. Its@theme inlineblock therefore generated no utilities but caused lightningcss to emitUnknown at rule: @themewarnings during build. The matching@theme inlineblock already lives inapp.css(which Tailwind does process), so the block here was pure duplication. The two variables actually referenced inside this file (--color-shop-green,--color-shop-orange, used by theshop-pulsekeyframes) are kept under:root.Stats
bg-opacity-50→bg-black/50: 1flex-shrink-0→shrink-0: 33bg-gradient-to-*→bg-linear-to-*: 60Verification
vite build: passes; theUnknown at rule: @themewarning (previously emitted twice) is gone.tsc --noEmit: passes.flex-shrink-0/bg-gradient-to-*/bg-opacity-*classes, new utilities render correctly, no visual regressions, and no CSS-related console errors.