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
I have some ideas on how to make IntelliSense support the v4 CDN properly but it'll be a bit before I can make that work. However, I did merge support for using v4 in projects that don't have it installed via npm. Once I tag the new version you can put the following in a CSS file (even if you don't otherwise use it):
@import"tailwindcss";
and it'll pick up the project as a v4 project. I'm aiming to tag the new release either today or tomorrow.
Case:
I am trying out tailwind css using CDN on a 1 page html, I installed the vs code plug in today and at the output it showed me :
[Info - 5:48:18 PM] [GLOBAL] No matching project for document {
fsPath: '/Users/markc/Documents/tailtest/tailwind.config.js',
normalPath: '/Users/markc/Documents/tailtest/tailwind.config.js'
}
Directory :
only 2 files
test01.html
tailwind.config.js
I would like to know what I should do to get intelliSense working ?
Thank you !
What version of VS Code are you using?
v1.96.4
What version of Tailwind CSS IntelliSense are you using?
v0.14.2
What version of Tailwind CSS are you using?
version":"4.0.3"
What package manager are you using?
npm
What operating system are you using?
Mac
Tailwind config
#I am testing a html using cdn , and I created an empty config.js file.
intelliSense setting
{ "workbench.colorTheme": "Default High Contrast",
"[tcl]": {},
"tcl.interpreterPath": "/Users/markc/Downloads/tcl9.0.0/macosx/configure",
"diffEditor.codeLens": true,
"geminicodeassist.project": "applied-shade-442902-b8",
"tailwindCSS.emmetCompletions": true,
"tailwindCSS.experimental.configFile": null,
"tailwindCSS.includeLanguages": {"html": "html","javascript": "javascript","css": "css"},
"editor.quickSuggestions": {
"strings": "on",
"comments": "inline"
},
"editor.inlineSuggest.enabled": true,
"files.associations": {
"*.css": "tailwindcss"
},}
The text was updated successfully, but these errors were encountered: