fix(blazor): pin Tailwind CSS to v3 to restore CI build#142
Merged
Conversation
Tailwind CSS v4 removed the CLI from the main package and changed @apply semantics (custom component classes can no longer be cross- referenced via @apply). Since the Blazor demo app's CSS extensively uses this pattern (~20 component classes), pin to v3 for now. A full v4 migration should be tracked as a separate issue.
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
1 participant
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
Pins
tailwindcssfrom^4.0.0back to^3.4.0to fix the CI build failure.Root Cause
Tailwind CSS v4 introduced breaking changes:
@tailwindcss/clipackage@applysemantics changed — Custom component classes defined in@layer componentscan no longer be cross-referenced via@applyThe Blazor demo app's CSS extensively uses cross-referenced
@apply(e.g.,.btn-primary { @apply btn ... },.toast-success { @apply toast ... }) across ~20 component classes, making a v4 migration non-trivial.Changes
package.json: Pintailwindcssto^3.4.0(was^4.0.0)package-lock.json: Updated lockfile for v3Testing
npm run build:csssucceeds locally with Tailwind v3wwwroot/css/output.cssDiscovered Issues
@utilitydirective or plain CSS instead of cross-referencing via@apply