Add `content` folder to tailwind paths by default

This issue has been tracked since 2022-10-18.

Is your feature request related to a problem? Please describe.

When using @nuxt/content, the content/ folder will not be checked by Tailwind's JIT engine by default.

Describe the solution you'd like

That it will be checked and classes will be generated

Describe alternatives you've considered

Adding it manually which is error-prone 🙈

Atinux wrote this answer on 2022-10-20

Actually it should be added by default, you can test with running yarn dev @manniL

See https://github.com/nuxt/content/blob/005fdfd19aa9658f821cb64a868d7f4d09582e1f/src/module.ts#L594-L597

manniL wrote this answer on 2022-10-20

Interesting! I'll have a deeper look once again and report back ☺️

manniL wrote this answer on 2022-10-20

Yes, my bad! The project still had tailwindcss as buildModule causing this behavior.
Maybe a warning for Nuxt3 users who accidentally use buildModules would make sense here?

Atinux wrote this answer on 2022-10-20

Don't you have the TS warning?
CleanShot 2022-10-19 at 15.56.28@2x.png

manniL wrote this answer on 2022-10-20

FYI: Was not my project. I see the deprecation when typing but not when actually using it
image
image

More Details About Repo
Owner Name nuxt-modules
Repo Name tailwindcss
Full Name nuxt-modules/tailwindcss
Language TypeScript
Created Date 2019-04-04
Updated Date 2023-03-29
Star Count 1285
Watcher Count 12
Fork Count 157
Issue Count 57

YOU MAY BE INTERESTED

Issue Title Created Date Updated Date