We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
theme()
What version of VS Code are you using? 1.93.1
What version of Tailwind CSS IntelliSense are you using? 0.13.38 (pre-release)
What version of Tailwind CSS are you using? 4.0.0-alpha.24
What package manager are you using? yarn
What operating system are you using? macOS Sonoma 14.6.1
Tailwind config Config file is empty but does exist.
VS Code settings
{ "tailwindCSS.experimental.configFile": "./app/tailwind.css" }
Reproduction URL https://github.com/boylett/tailwind-v4-theme-in-css-modules-demo/blob/main/app/routes/index.module.css Note that this is happening inside a CSS Module despite the config import.
Describe your issue Intellisense claims an invalid config path when there is whitespace after a range syntax comparator.
If I remove the whitespace the error disappears, albeit with no annotations.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
What version of VS Code are you using?
1.93.1
What version of Tailwind CSS IntelliSense are you using?
0.13.38 (pre-release)
What version of Tailwind CSS are you using?
4.0.0-alpha.24
What package manager are you using?
yarn
What operating system are you using?
macOS Sonoma 14.6.1
Tailwind config
Config file is empty but does exist.
VS Code settings
Reproduction URL
https://github.com/boylett/tailwind-v4-theme-in-css-modules-demo/blob/main/app/routes/index.module.css
Note that this is happening inside a CSS Module despite the config import.
Describe your issue
Intellisense claims an invalid config path when there is whitespace after a range syntax comparator.
If I remove the whitespace the error disappears, albeit with no annotations.
The text was updated successfully, but these errors were encountered: