Fix Tailwind CSS v4 plugin configuration syntax #9
+12
−5
Conversation
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
The current @plugin syntax was using `,` (comma) which is incorrect syntax and will fail parsing. This changes it to use `;` (semi-colon) instead. We also add pragmas to stop Prettier from running on these lines and changing the casing on the keys, which will cause the configuration to not work. Prettier usage is an extremely common, so this is why it is added by default.
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.
The current @plugin syntax was using
,(comma) which is incorrect syntax and will fail parsing. This changes it to use;(semi-colon) instead.We also add pragmas to stop Prettier from running on these lines and changing the casing on the keys, which will cause the configuration to not work. Prettier usage is an extremely common, so this is why it is added by default.
I can remove the
/* prettier-ignore */from the PR if you feel like it doesn't make sense to have here :)