@tailwind error in `globals.css`
Answered
Cape lion posted this in #help-forum
Cape lionOP
I created a next project (
When visiting the
How do I fix this? No changes has been made to the project, it's just the
npm create-next-app) with tailwind, typescript and /app dir (without /src dir). When visiting the
globals.css file in the /app dir, the first three lines including @tailwind show the same error, which can be seen in the attached screenshot. How do I fix this? No changes has been made to the project, it's just the
create-next-app with the configuration above.Answered by DirtyCajunRice | AppDir
this is not a bug. this is vscaca shitting the bed
5 Replies
@Cape lion I created a next project (`npm create-next-app`) with `tailwind`, `typescript` and `/app` dir (without `/src dir`).
When visiting the `globals.css` file in the `/app` dir, the first three lines including `@tailwind` show the same error, which can be seen in the attached screenshot.
How do I fix this? No changes has been made to the project, it's just the `create-next-app` with the configuration above.
this is not a bug. this is vscaca shitting the bed
Answer
@DirtyCajunRice | AppDir this is not a bug. this is vscaca shitting the bed
Cape lionOP
VSCode moment
Vscode users need to also setup their editor as well https://tailwindcss.com/docs/editor-setup#syntax-support. Or just ignore this error, it’s harmless
The error is due to the directive being invalid css, but the file will be processed by postcss to become a valid css file so it’s harmless
@joulev Vscode users need to also setup their editor as well <https://tailwindcss.com/docs/editor-setup#syntax-support>. Or just ignore this error, it’s harmless
Cape lionOP
Thank you for the clarification!