Replace fake data with real one
Signed-off-by: Al Asad Nur Riyad <asadnurriyad@gmail.com>
This commit is contained in:
@@ -6,19 +6,19 @@ image: /nuxt-blog/pexels-photo-157040_gwfamn.jpg
|
||||
alt: Hwo to fix tailwind intellisense in nuxt3 project
|
||||
ogImage: /nuxt-blog/pexels-photo-157040_gwfamn.jpg
|
||||
provider: cloudinary
|
||||
tags: ['nuxt', 'vue', 'tailwind']
|
||||
tags: ['nuxt', 'tailwindcss']
|
||||
published: true
|
||||
---
|
||||
|
||||
## Problems
|
||||
### Problems
|
||||
|
||||
I had a Nuxt3 and TailwindCSS project. which was opened in VsCode. But the problem was, in my project the tailwind intellisense didn't working properly. I tried to reinstall the vscode tailwind extension but the problem didn't solve properly. Later after doing some research I found a [workaround](https://github.com/tailwindlabs/tailwindcss-intellisense/issues/663#issuecomment-1316788128), That I am sharing here today.
|
||||
|
||||
## Why It's Not working
|
||||
### Why It's Not working
|
||||
|
||||
In our nuxt project we have a `.nuxt` directory. Nuxt uses the `.nuxt/` directory in development to generate your Vue application. And if we try to look properly there is also a file called `.nuxt/tailwind.config.cjs`, So tailwind find to config file in the same project, one is in your root directory and another one is in you `.nuxt` directory.
|
||||
|
||||
## Possible Workaround
|
||||
### Possible Workaround
|
||||
|
||||
One possible solution is, In your project we call tell the extension to exclude the `.nuxt` directory. To exclude the `.nuxt` directory in your workspace,
|
||||
|
||||
|
||||
Reference in New Issue
Block a user