-
Notifications
You must be signed in to change notification settings - Fork 87
Upgrade Tailwind to v4.1 #8072
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?
Upgrade Tailwind to v4.1 #8072
Conversation
By running `npx @tailwindcss/upgrade`, then fixing `*.module.css` files that had no `@reference` which is a new thing, then moving the code-mirror override selectors and a few other things out of the utility layer that the migration script moved them into. Sorry it's all in one commit, the first script touched so many files I should have committed immediately.
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Found a couple gotchas with border-radii on the home page project cards, and in the status bar something fiddly is off with the help menu button. These point toward a couple spots where the migration might not have worked quite right; needs more of a comb-through before I mark as ready. |
Thank you for these @jacebrowning and @max-mrgrsk! |
Some chore work that will help me in some design token / design system work I'm exploring right now.
@reference
s to our*.module.css
files per this page. I wish I could use our@src
alias here but it looked like I could only use relative syntax@utility
s or@layer utilities
where it was inappropriate. The biggest was the selectors around the#codemirror-overrides
ID. I decided to just move these into their own file and@import
them at the top of theindex.css
file while I was making the change.The idea here is that nothing should break or look visually wrong after this migration. Please help me scour the app to find any other styles that appear broken before this merges.