Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Intellisense with multiple tailwind configs doesn't work correctly #1108

Open
artaommahe opened this issue Dec 10, 2024 · 0 comments
Open

Intellisense with multiple tailwind configs doesn't work correctly #1108

artaommahe opened this issue Dec 10, 2024 · 0 comments

Comments

@artaommahe
Copy link

artaommahe commented Dec 10, 2024

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

  • clone
  • npm install
  • npm run dev
  • see that everything looks like expected
    image
  • 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
image

same with colors, secondary border and p-2 are not recognized
image

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant