Skip to content

Bump tailwindcss from 4.1.18 to 4.3.3 #98

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
+79 −5
Open

Bump tailwindcss from 4.1.18 to 4.3.3 #98

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
82 changes: 78 additions & 4 deletions package-lock.json
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

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 @@ -123,6 +123,6 @@
"react": "^19.0.1",
"react-dom": "^19.0.1",
"rimraf": "^6.1.2",
"tailwindcss": "^4.1.18"
"tailwindcss": "^4.3.3"

@cursor cursor Bot Jul 16, 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.

CLI still on older Tailwind

Medium Severity

Bumping only the direct tailwindcss devDependency to ^4.3.3 leaves @tailwindcss/cli at ^4.1.18. Scripts such as css:build and dev run the CLI’s tailwindcss binary, which resolves the nested tailwindcss 4.1.18 from the lockfile, so generated CSS still uses 4.1.18 despite the declared 4.3.3 upgrade.

Additional Locations (1)
Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 1ab84a8. Configure here.

}
}