Replies: 1 comment 1 reply
-
|
Hey! Moved this to an ideas discussion because this currently isn't a bug but more like a missing feature. Right now the canonicalization process is relatively complex (and slow to setup), and to make things simpler we only canonicalize classes in groups based on their used variants. So in your case, we will only canonicalize 2 groups: There are some other internal pending things we need to do before we can explore this bigger search space. For now, I'll keep this as a future suggestion instead of a bug since the classes going in are still valid and should still work as expected. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
What version of Tailwind CSS are you using?
v4.3.0
What build tool (or framework if it abstracts the build tool) are you using?
N/A
What version of Node.js are you using?
v24
What browser are you using?
N/A
What operating system are you using?
N/A
Reproduction URL
Repository, see
at-apply-with-breakpoint.mjsRun with
npm install && npm run at-apply-with-breakpointDescribe your issue
Discovered by using eslint-plugin-better-tailwindcss.
Using breakpoints in utility classes (via apply) breaks the canonical classes discovery. Example:
The
md:text-[15px]part is the breaking one. If it gets removed, everything works just fine.Or a more complex (real life) example:
Beta Was this translation helpful? Give feedback.
All reactions