chore: remove unused browserslist config#185
Conversation
The browserslist config was consumed by autoprefixer, which is redundant with Tailwind CSS v4 (Lightning CSS handles prefixing natively). With autoprefixer being removed (PR #180), browserslist has no consumer in this project — Vite/esbuild, @vitejs/plugin-react, and @tailwindcss/postcss do not use browserslist. No behavior change — CSS prefixing is already handled by Lightning CSS within @tailwindcss/postcss.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 9a941e1e0d
ℹ️ 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".
| "not ie <= 11", | ||
| "not op_mini all" | ||
| ], | ||
| "keywords": [ |
There was a problem hiding this comment.
In this commit the Browserslist block is removed, but this repo still imports and executes autoprefixer from postcss.config.js (plugins: [tailwindcss, autoprefixer]). For any build of this commit before the promised Autoprefixer-removal change lands, Autoprefixer still consumes Browserslist and will fall back to its default targets instead of the project’s explicit >0.2%, not dead, not ie <= 11, not op_mini all policy, so production CSS prefixing can change even though the commit claims there is no CSS-processing change.
Useful? React with 👍 / 👎.
1 participant
Summary
Removes the
browserslistfield frompackage.json— it has no consumer in this project after Tailwind CSS v4 migration.Why
The
browserslistconfig was previously consumed byautoprefixerto determine which vendor prefixes to add. With Tailwind CSS v4:@tailwindcss/postcss) handles vendor prefixing nativelyautoprefixeris redundant and is being removed in PR chore: remove redundant autoprefixer dependency #180browserslist— it usesbuild.target(defaults tomodules)@vitejs/plugin-reactdoes not usebrowserslistby default (no Babel config in this project)Without any consumer, the
browserslistfield is dead configuration.Changes
package.json: Removedbrowserslistkey with 4 entriesTest Plan
@tailwindcss/postcss