-
Notifications
You must be signed in to change notification settings - Fork 129
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conflict with other Prettier plugins, specifically prettier-plugin-tailwind #117
Comments
Same Issue with the official tailwindlabs/prettier-plugin-tailwindcss |
This issue has been revealed other github issue, the official tailwindlabs/prettier-plugin-tailwindcss. According to the under the link, the comment suggest that fix the「prettier.config.js」file and then result in the work, can work both 「prettier-plugin-sort-imports」 and 「prettier-plugin-tailwindcss」libraries 🚀 The suggestion in prettier-plugin-tailwindcss: so, thank you, and for developing good sorts plugin!!! Trivago teams is the best working in developers market☀️ again, 【My Settings: prettier.config.js】
|
The above solution doesn't work for me. In my Vue SFC files it still doesn't sort the tailwind css |
It also does not work for me in a Next.js app, but it seems like your config is for Next? |
following along, have the same problem. seems like whichever gets imported first in the
|
Your Environment
Describe the bug
When used with prettier-plugin-tailwind, that plugin does not format tailwind. The two conflict and this one takes precedence solely based on the alphabetic order of the plugin names. There is an issue open with more details in prettier-plugin-tailwind. It seems to be a limitation in Prettier plugin API.
If someone uses this with a conflicting plugin that happens to be alphabetically earlier than this one, then this one will stop working. Hopefully this issue helps someone understand their problem. Perhaps add a mention of this to Readme?
To Reproduce
Expected behavior
Imports are sorted, Tailwind class names are sorted.
The text was updated successfully, but these errors were encountered: