-
Notifications
You must be signed in to change notification settings - Fork 195
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 won't work with a Nuxt3 project with a .tailwind.config.ts (typescript) file #591
Comments
This is because Tailwind CSS does not currently support TypeScript config files. We'd need to do a good bit of tooling work to support it. My guess is that Nuxt is compiling the I gave a short explanation on why we don't (yet) support .ts files here: tailwindlabs/tailwindcss#7327 (comment) |
Sorry! I had no clue. I guess I got confused by their docs. Have a nice day! |
As of |
@P4sca1 had no effect for me. Using Nuxt 3.0.0 and latest @nuxtjs/tailwindcss |
Have you started Nuxt one time so that the file gets generated?you might need to reload VSCode afterwards. |
@P4sca1 i've reloaded VSCode completely, then restarted nuxt with |
Yes, it works for me. You can check whether the tailwind.config.cjs file gets generated at the correct location. |
@P4sca1 yeah, it is located under this path: .nuxt/tailwind.config.cjs |
What version of Tailwind CSS IntelliSense are you using?
v0.8.6
What version of Tailwind CSS are you using?
I'm using
@nuxtjs/tailwindcss v5.3.1
, which resolves to v3.1.8What package manager are you using?
npm
What operating system are you using?
Ubuntu 22.04
Describe your issue
To reproduce, to the following:
tailwind.config.ts
file (Typescript) like the following:TailwindCSS Intellisense outputs the following (extension outputs):
Now, simply change the
.ts
file into a.js
file, like so:And tadah! This works. The extension outputs:
This simply means I'll just use a
.js
file as it changes nothing but this made me lose my mind for a couple of hours, so I'm opening this issue.The text was updated successfully, but these errors were encountered: