Skip to content
This repository was archived by the owner on Aug 25, 2026. It is now read-only.

Update dependency tailwindcss to v4 #278

Closed
renovate wants to merge 1 commit into from
Closed

Update dependency tailwindcss to v4 #278

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Binary file modified frontend/bun.lockb
View file
Open in desktop
Binary file not shown.
2 changes: 1 addition & 1 deletion frontend/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -63,7 +63,7 @@
"@types/react": "^18",
"autoprefixer": "^10.0.1",
"postcss": "^8",
"tailwindcss": "^3.3.5",
"tailwindcss": "^4.0.0",

@cursor cursor Bot May 9, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tailwind v4 upgrade breaks incompatible v3 PostCSS config

High Severity

Bumping tailwindcss to v4 without migrating the project's configuration will break the build entirely. Tailwind v4 no longer exports a PostCSS plugin from the tailwindcss package (it moved to @tailwindcss/postcss), so postcss.config.js referencing tailwindcss as a plugin will fail. Additionally, globals.css uses v3 directives (@tailwind base/components/utilities), and tailwind.config.ts uses v3-only features like require("tailwindcss-animate"), content array, darkMode, and the <alpha-value> color syntax — none of which are compatible with v4 without a compatibility layer.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 5f1eb95. Configure here.

"typescript": "^5.3.3"
}
}