Skip to content
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 #44

Closed
denis-sokolov opened this issue Nov 30, 2021 · 3 comments

Comments

@denis-sokolov
Copy link

When used with prettier-plugin-tailwind, this plugin does not organize imports. There is an issue open in prettier-plugin-tailwind. It seems to be a limitation in Prettier plugin API.

Hopefully this issue helps someone understand their problem. Perhaps add a mention of this to Readme?

@simonhaenisch
Copy link
Owner

Hm apparently I misunderstood how Prettier loads plugins... yeah doesn't seem like it can be fixed.

I'll add an info to the readme about this behavior.

@pwespi
Copy link

pwespi commented Jan 27, 2022

Related to tailwindlabs/prettier-plugin-tailwindcss#26, which also contains a workaround to make this plugin work with prettier-plugin-tailwindcss.

@chalkygames123
Copy link

chalkygames123 commented Oct 31, 2022

@denis-sokolov Thank you, I spent a whole day trying to figure out what was going on and finally got here.

For those looking for an easy solution, I would recommend eslint-plugin-tailwindcss as a more comprehensive alternative. But note that the classnames-order rule is not working with the latest Tailwind CSS. See: francoismassart/eslint-plugin-tailwindcss#173

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants