Throw a useful error when tailwindcss is used as a PostCSS plugin#14378
Merged
philipp-spiess merged 9 commits intoSep 11, 2024
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
adamwathan
reviewed
Sep 11, 2024
Co-authored-by: Adam Wathan <adam.wathan@gmail.com>
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
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.
While upgrading a project to Tailwind CSS v4, I forgot to remove the
tailwindcssimport from the PostCSS config. As a result of this, I was greeted with the following message:I don't think this was particularly helpful, so I’m proposing we add a default function export to the
tailwindcsspackage so when it's used inside PostCSS, we can control the error message. So I changed it to something along these lines:This is also a good place to link to the migration guides once we have them 🙂