Tailwind v4 integration#27
Merged
Merged
Conversation
Co-authored-by: me <me@kentcdodds.com>
Co-authored-by: me <me@kentcdodds.com>
|
Cursor Agent can help with this pull request. Just |
- Fix container max-width to trigger at 1536px (2xl breakpoint) instead of 1400px to match original Tailwind v3 behavior - Remove unused borderColor property from extendedTheme
|
Bugbot Autofix resolved 2 of the 2 bugs found in the latest run.
|
|
Bugbot Autofix resolved the bug found in the latest run.
|
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
Upgrades the project to Tailwind CSS v4, removing
postcssandtailwind.config.tsin favor of the new@tailwindcss/viteplugin and CSS-only configuration.Key changes include:
@tailwindcss/viteplugin.app/styles/tailwind.cssusing@themeand@utilitydirectives.components.jsonupdated to point shadcn to the CSS-only config.app/utils/extended-theme.tsfortailwind-merge.Test Plan
npm run buildto confirm the production build pipeline functions as expected with the new Tailwind setup. (Log attached)Checklist
Screenshots
Homepage renders with Tailwind v4 styles.
Build Log:
npm run buildoutput: /opt/cursor/artifacts/npm-run-build.logNote
Medium Risk
Build/styling pipeline changes (Tailwind major version + new Vite integration) can cause widespread visual regressions or missing utilities if any tokens/plugins were not migrated correctly.
Overview
Upgrades the app to Tailwind CSS v4 by switching from a PostCSS +
tailwind.config.tssetup to the@tailwindcss/viteplugin.Theme configuration is migrated into
app/styles/tailwind.css(CSS variables,@themetokens for colors/typography/animations, customcontainerutility, and adarkvariant), and the old marketing preset/config files are removed.Dependencies are updated accordingly (add
@tailwindcss/viteandtw-animate-css, bumptailwindcss/tailwind-merge, remove legacy Tailwind/PostCSS-related packages) andcomponents.jsonis adjusted for shadcn to use CSS-only config.Written by Cursor Bugbot for commit 3dce529. This will update automatically on new commits. Configure here.