Closed eramsayCB closed 6 months ago
This is not the case in my project. Seeing ordering like ml-0.5 mr-2 mt-1.5 size-3 self-start
. So it might be to do with dependencies (or sub-dependencies) in your project.
You can try creating a new repo to reproduce this behaviour and then build it up step by step. This will help you reveal the peculiarity of your project.
This is not the case in my project. Seeing ordering like
ml-0.5 mr-2 mt-1.5 size-3 self-start
. So it might be to do with dependencies (or sub-dependencies) in your project.You can try creating a new repo to reproduce this behaviour and then build it up step by step. This will help you reveal the peculiarity of your project.
Thanks @kachkaev. After seeing your comment I dug into it a bit further and believe I have conflicting linter rules between my packages/configs for this project and my VSCode IDE plugins. Closing this bug out.
Thanks again!
Describe the bug
size-*
utilities from the latest tailwindcss@v3.4 release appear to be treated as custom classnames in classname-order rule set, which when auto-resolved moves allsize
classes to the beginning of the classname string, ignoring responsive utilities (e.g.md:size-44
)To Reproduce Steps to reproduce the behavior: Add responsive
size
utilities classes to the end of a classname string:Auto-resolve the warning according to the linter rule set, and responsive classes move to front of string like custom classnames:
Expected behavior Expect responsive
size
utility classes to align with other responsive classnames without displaying a warning:order-1 size-44 min-w-fit md:size-56 lg:order-2 lg:size-64 xl:size-72 2xl:size-[336px] 3xl:size-[theme(maxWidth.md)]
Screenshots If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):
Additional context Add any other context about the problem here.
eslint config file or live demo
.eslintrc.js file...