Repository navigation
Add Tailwind v4 migration case study - #18
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
First real-world run of renderdiff: the Tailwind v3 → v4 migration of timlrx/tailwind-nextjs-starter-blog (PRs #1111 and #1122), last v3 commit vs post-migration commit, both production-built locally. 11 routes × 5 widths.
docs/case-study.md: commands, trimmed real output from the first and final runs, the agent loop (fix →--rerun-failed→--accept), what it caught, what it got wrong, runtime.docs/img/case-study/: three real crops from run 1.Headline: it caught two layout regressions the migration shipped (a 4px
/aboutshift from v4'sspace-xselector change, still on upstream main, and a 4px header-nav shift atsm+), and it missed a visible brand-pink change because the pixel threshold treats it as the same colour. The "What it got wrong" section lists that miss and four rough edges (phantom bands, noisydomproperties, a flaky CSP error, unacceptableh-1 unalignedshots).README is untouched.
🤖 Generated with Claude Code