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
open NewDesignComponent and Button components in vscode
see that colors are wrong and for some tokens there is no autocompletion and highlighting
border should be red, bg black, text white, p-4 bigger, etc
same with colors, secondary border and p-2 are not recognized
Describe your issue
In our project we're on a way of slow migration from the old messy design system (set in the main tailwind config) to the new shinny one (set in another config). While tailwind itself recognizes both configs and there corresponding content files properly and all the colors and other values are correct in the browser, the vscode extension struggles here and sometimes shows correct (new) values for new-design/* and ui-kit/* components, sometimes not. In the reproduction repo it even always shows the old values for some reason.
The text was updated successfully, but these errors were encountered:
What version of VS Code are you using?
Version: 1.95.3 (Universal)
What version of Tailwind CSS IntelliSense are you using?
v0.12.16
What version of Tailwind CSS are you using?
v3.4.16
What package manager are you using?
npm
What operating system are you using?
macOS 15.1.1 (24B91)
Tailwind config
VS Code settings
nothing tailwind- or extension-related was changed
Reproduction URL
https://github.com/artaommahe/tailwind-intellisense-multiple-configs
NewDesignComponent
andButton
components in vscodeborder should be red, bg black, text white, p-4 bigger, etc
same with colors, secondary border and p-2 are not recognized
Describe your issue
In our project we're on a way of slow migration from the old messy design system (set in the main tailwind config) to the new shinny one (set in another config). While tailwind itself recognizes both configs and there corresponding content files properly and all the colors and other values are correct in the browser, the vscode extension struggles here and sometimes shows correct (new) values for
new-design/*
andui-kit/*
components, sometimes not. In the reproduction repo it even always shows the old values for some reason.The text was updated successfully, but these errors were encountered: