chore: upgrade Tailwind CSS to v4.3.3 and migrate to Tailwind v4 syntax conventions - #831
Open
karticme wants to merge 2 commits into
Open
chore: upgrade Tailwind CSS to v4.3.3 and migrate to Tailwind v4 syntax conventions#831karticme wants to merge 2 commits into
karticme wants to merge 2 commits into
Conversation
|
@karticme is attempting to deploy a commit to the cal Team on Vercel. A member of the Team first needs to authorize it. |
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
Runs the official
@tailwindcss/upgradecodemod across the monorepo to adopt Tailwind CSS v4 and its updated utility naming conventions. No visual changes are intended — this is a mechanical migration.What changed
Package version
tailwindcssto^4.3.3in the root andpackages/uimanifests.CSS syntax (
globals.css)!importantmodifier moved to suffix position —!mt-0→mt-0!(Tailwind v4 convention).@utility container { … }block repositioned above@layer components(v4 ordering requirement).Logical property class renames (335 files)
The codemod replaced deprecated directional aliases with their CSS logical property equivalents across all component files, registry components, and compiled JSON registry outputs:
start-pxinset-s-pxend-0inset-e-0end-0.5inset-e-0.5Files affected
apps/ui/registry/default/ui/—combobox,alert,autocomplete,calendar,command,dialog,drawer,group,sheet,sidebar,toggle-groupapps/ui/registry/default/particles/— various particle componentsapps/ui/public/r/— compiled JSON registry entriesapps/origin/registry/default/— all origin UI and component files (~200+ files)apps/examples/calcom/— example app componentspackages/ui/src/components/— published package componentspackages/ui/src/styles/globals.css— base stylesheetNotes
useSortedClasseslint rule flagged the reordered class names introduced by the codemod. All sort violations were auto-fixed withbiome check --write --unsafebefore committing so the pre-commit hook passes cleanly.Testing
apps/uiandapps/origindev servers — all affected classes are logical-property equivalents and should render identically in LTR layouts.