You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What version of prettier-plugin-tailwindcss are you using?
v0.6.5
What version of Tailwind CSS are you using?
v3.4.1
What version of Node.js are you using?
v20.11.0
What package manager are you using?
pnpm
What operating system are you using?
Windows
Describe your issue
If i use the custom style in a css/less file, an error will occur once formatted.
If i don't use ~“” to wrap the custom style ( @apply ~"tw-right-[20px]" ), there's no problem, but the custom style cannot take effect.
Before format
After format
Describe the problem you're seeing, any important steps to reproduce and what behavior you expect instead.
The text was updated successfully, but these errors were encountered:
gwh18560
changed the title
When I use custom styles in CSS/LESS files, formatting will report an error
When I use custom styles in CSS/LESS files, formatting will make an error
Oct 18, 2024
This also happens for any custom classes added to the tailwind config. Prettier is suggesting to put bg-scrim as the 1st class while the sorter places it last
I am seeing this as well with my custom color. For some reason the vscode prettier extension and prettier cli disagree on the class sorting. I am using [email protected] and [email protected]. Note that this ONLY happens with my custom color. If I change bg-paper to bg-red-500 the bug goes away.
What version of
prettier-plugin-tailwindcss
are you using?v0.6.5
What version of Tailwind CSS are you using?
v3.4.1
What version of Node.js are you using?
v20.11.0
What package manager are you using?
pnpm
What operating system are you using?
Windows
Describe your issue
If i use the custom style in a css/less file, an error will occur once formatted.
If i don't use
~“”
to wrap the custom style (@apply ~"tw-right-[20px]"
), there's no problem, but the custom style cannot take effect.Before format
After format
Describe the problem you're seeing, any important steps to reproduce and what behavior you expect instead.
The text was updated successfully, but these errors were encountered: