[andrerfneves]

Summary

Tailwind CSS v4's @tailwindcss/postcss plugin uses Lightning CSS internally, which handles vendor prefixing automatically. The separate autoprefixer PostCSS plugin and its devDependency are unnecessary.

Problem

• Tailwind v4 with @tailwindcss/postcss already includes Lightning CSS which adds vendor prefixes
• The standalone autoprefixer PostCSS plugin is redundant
• It adds an unnecessary dependency and build step

Changes

• Remove autoprefixer import and plugin from postcss.config.js
• Remove autoprefixer from package.json devDependencies

Verification

• All 52 tests pass
• npm run build completes successfully
• CSS vendor prefixes are still applied (Lightning CSS handles this)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
lightning-decoder	Ready	Preview, Comment	Jun 9, 2026 6:05pm

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 5b0085de4c

ℹ️ 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".

[chatgpt-codex-connector]

Update the lockfile when dropping autoprefixer

Removing this devDependency from package.json without updating package-lock.json leaves the root lockfile devDependencies entry and node_modules/autoprefixer package record intact. I checked the repo's npm workflow with npm ci --dry-run, and it still plans to install autoprefixer, so clean CI installs continue carrying the dependency this commit is meant to remove; please regenerate and commit the lockfile with the package removed.

Useful? React with 👍 / 👎.