Skip to content

chore(deps-dev): bump tailwindcss from 3.4.19 to 4.2.1 #15

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.

Sign up for GitHub

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

Open
dependabot wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore(deps-dev): bump tailwindcss from 3.4.19 to 4.2.1 #15

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
2 changes: 1 addition & 1 deletion package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -62,7 +62,7 @@
"playwright-core": "^1.58.1",
"postcss": "^8.4.35",
"prettier": "^3.2.0",
"tailwindcss": "^3.4.1",
"tailwindcss": "^4.2.1",
Copy link
Copy Markdown

@cubic-dev-ai cubic-dev-ai Bot Mar 5, 2026 •
edited
Loading

Choose a reason for hiding this comment

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

P0: Breaking change: This bumps Tailwind CSS from v3 to v4, a major version with extensive breaking changes, but no migration steps were applied. The build will fail because:

  • postcss.config.js still references tailwindcss as the PostCSS plugin, but v4 requires the separate @tailwindcss/postcss package (not installed)
  • tailwind.config.js uses the v3 JS config format (module.exports, content, theme.extend, plugins: [require('tailwindcss-animate')]), which v4 replaced with CSS-first configuration (@theme directives)
  • tailwindcss-animate ^1.0.7 uses the v3 plugin API, incompatible with v4

Per the official upgrade guide, you should run npx @tailwindcss/upgrade to automate most migration, or revert to v3 until the project is ready to migrate.

Prompt for AI agents 
Check if this issue is valid — if so, understand the root cause and fix it. At package.json, line 65:

<comment>**Breaking change**: This bumps Tailwind CSS from v3 to v4, a major version with extensive breaking changes, but no migration steps were applied. The build will fail because:

- `postcss.config.js` still references `tailwindcss` as the PostCSS plugin, but v4 requires the separate `@tailwindcss/postcss` package (not installed)
- `tailwind.config.js` uses the v3 JS config format (`module.exports`, `content`, `theme.extend`, `plugins: [require('tailwindcss-animate')]`), which v4 replaced with CSS-first configuration (`@theme` directives)
- `tailwindcss-animate` ^1.0.7 uses the v3 plugin API, incompatible with v4

Per the [official upgrade guide](https://tailwindcss.com/docs/upgrade-guide), you should run `npx @tailwindcss/upgrade` to automate most migration, or revert to v3 until the project is ready to migrate.</comment>

<file context>
@@ -62,7 +62,7 @@
     "postcss": "^8.4.35",
     "prettier": "^3.2.0",
-    "tailwindcss": "^3.4.1",
+    "tailwindcss": "^4.2.1",
     "tailwindcss-animate": "^1.0.7",
     "tsx": "^4.7.0",
</file context>
Suggested change
"tailwindcss": "^4.2.1",
"tailwindcss": "^3.4.1",
Fix with Cubic

"tailwindcss-animate": "^1.0.7",
"tsx": "^4.7.0",
"typescript": "^5.3.0",
Expand Down
Loading