Skip to content

chore(deps): upgrade Tailwind to v4 - #8

Merged
jevin98 merged 3 commits into
mainfrom
codex/upgrade-tailwind-v4
May 14, 2026
Merged

chore(deps): upgrade Tailwind to v4#8
jevin98 merged 3 commits into
mainfrom
codex/upgrade-tailwind-v4

Conversation

@jevin98

Copy link
Copy Markdown
Owner

Summary

  • Upgrade Tailwind CSS from v3.4.17 to v4.3.0.
  • Use the WXT/Tailwind v4 Vite integration via @tailwindcss/vite in wxt.config.ts.
  • Replace legacy @tailwind directives with @import "tailwindcss".
  • Remove obsolete Tailwind v3/PostCSS config files.

Why

WXT latest examples for Tailwind v4 integrate Tailwind through the Vite plugin because WXT owns the Vite configuration. This keeps the project aligned with the current WXT + Tailwind v4 setup.

Validation

  • pnpm compile
  • pnpm build

Note: the Firefox build emits WXT's data collection permission warning, but all browser targets build successfully.

@jevin98

Copy link
Copy Markdown
OwnerAuthor

@codex review

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. 👍

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

…d-v4
# Conflicts:
#	postcss.config.js
#	tailwind.config.js
@jevin98
jevin98 merged commit dfeadc7 into mainMay 14, 2026
@jevin98
jevin98 deleted the codex/upgrade-tailwind-v4 branch May 15, 2026 03:51
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@jevin98