Remove autoprefixer as peer-dependency #7949
Merged
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.
We list autoprefixer as a peer-dependency because it's used by the CLI, but it's not actually needed by Tailwind itself. If you are using a build tool other than our CLI, you might not need it at all (for example Parcel handles vendor prefixing on its own without autoprefixer), so users aren't actually always required to install it.
This makes our handling of autoprefixer and cssnano consistent, which are both used by the CLI but autoprefixer was marked as a peer-dependency and cssnano wasn't. We compile these peer-dependencies into what we distribute via npm anyways so that there's a fallback available if people don't install them (for instance using
npx tailwindcss
without installing Tailwind locally) so everything will continue to work fine anyways./cc @devongovett