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 Tailwind CSS IntelliSense are you using?
v0.12.6
What version of Tailwind CSS are you using?
3.4.7
What package manager are you using?
npm
What operating system are you using?
macOs
Describe your issue
I'm building a design system with tailwindcss and class variance authority (CVA) where some components have many different variants. We are also using design tokens with long names.
When the tailwind variants object and classes gets too big, tailwind intellisense, hovering and autocomplete stop working.
This apparently has something do with the searchRange (See #837)
I understand this was increased but it still doesn't work for many options.
Is this configureable? Is there anything that can be done to fix it?
But both of those tickets are closed so not sure if the conversation is surfacing. Could we expand the searchRange to be unlimited? E.g. just scan the whole file? Or at least significantly (like, an order of magnitude) longer?
If there's some editor performance issues with making the searchRange unlimited, being able to configure it for your certain use case is also fine. Just would really appreciate a solution because tailwind without the intellisense is totally different and degraded DX
What version of VS Code are you using?
1.92
What version of Tailwind CSS IntelliSense are you using?
v0.12.6
What version of Tailwind CSS are you using?
3.4.7
What package manager are you using?
npm
What operating system are you using?
macOs
Describe your issue
I'm building a design system with tailwindcss and class variance authority (CVA) where some components have many different variants. We are also using design tokens with long names.
When the tailwind variants object and classes gets too big, tailwind intellisense, hovering and autocomplete stop working.
This apparently has something do with the searchRange (See #837)
I understand this was increased but it still doesn't work for many options.
Is this configureable? Is there anything that can be done to fix it?
Code example that fails
The text was updated successfully, but these errors were encountered: