Repository navigation
feat: upgrade tailwindcss to v4 - #34
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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
tailwindcss3.3.3 -> 4.3.3, via the official@tailwindcss/upgradecodemod.tailwind.config.tsdeleted — the theme now lives in@themeinsideapp/globals.css@tailwind base/components/utilities->@import 'tailwindcss'postcss.config.js->@tailwindcss/postcssautoprefixerremoved — v4 handles prefixing itselftailwindcss-animatekept, loaded via@pluginVerification
The visual surface has no automated coverage — the e2e suite asserts status codes and headers,
not styles — and the styled page sits behind Clerk auth, so screenshots cannot reach it. So
rather than rely on "it builds", I compared the compiled CSS before and after: every
utility the source uses, checked against the emitted bundle.
107 utilities identical. 11 changed — each a documented v4 rename with a 1:1 counterpart:
focus-visible:outline-nonefocus-visible:outline-hiddenoutline-nonechanged meaning in v4focus:outline-nonefocus:outline-hiddenshadowshadow-xsz-[100]z-100group-[.destructive]:hover:*hover:group-[.destructive]:*group-[.destructive]:focus:*focus:group-[.destructive]:*Nothing was silently dropped — no utility lost its rule without a renamed equivalent.
The publicly reachable styled page also renders byte-identically: screenshots of
/sign-inbefore and after share the same SHA-256 (
df43cae23aac967c…).What is still unverified
The authenticated
/page —UrlForm,UrlList, the table, buttons and toasts — is where mostTailwind classes actually render, and no automated check reaches it. The CSS comparison covers
those utilities at the stylesheet level, but nobody has looked at the rendered page.
Worth clicking through the preview signed in before merging.
Testing
pnpm build— compilespnpm test:unit— 18 passedpnpm test:e2e— 9 passedpnpm lint/pnpm format:check— clean