chore: remove redundant autoprefixer PostCSS plugin#211
Open
andrerfneves wants to merge 1 commit into
Open
Conversation
With Tailwind CSS v4, the @tailwindcss/postcss plugin uses Lightning CSS which handles vendor prefixing internally. The separate autoprefixer PostCSS plugin is now redundant and was only kept as dead config after the Tailwind v3->v4 migration. PR #185 removed the browserslist config that autoprefixer depended on but this autoprefixer cleanup was deferred. Removing it: - Eliminates an unnecessary PostCSS processing pass on every build - Removes the unused autoprefixer devDependency - Has no effect on the built CSS (Lightning CSS already handles prefixes)
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Removes the redundant
autoprefixerPostCSS plugin frompostcss.config.jsand theautoprefixerdevDependency frompackage.json.Why
With Tailwind CSS v4, the
@tailwindcss/postcssplugin uses Lightning CSS internally, which handles vendor prefixing automatically. The separateautoprefixerPostCSS plugin was left over from the Tailwind v3 → v4 migration and is now redundant:browserslistconfig that autoprefixer depended on@tailwindcss/postcss) produces the same prefixed output, making a second prefixing pass unnecessaryChanges
postcss.config.js: Removed theautoprefixerimport and plugin entrypackage.json: RemovedautoprefixerfromdevDependenciespackage-lock.json: Regenerated (autoprefixer removed from lockfile)Test Plan
@tailwindcss/postcss)