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
Now that Nuxt 4 is on the horizon, according to the new directory structure, should we move Tailwind config to the app folder, considering that Tailwind CSS is a frontend thing?
The doc says this module looks for config file under the root path by default. Should this be changed as well? Or I have to update Nuxt config if I want to try out features of Nuxt 4:
Hi, thanks for opening an issue on this repository. It's certainly interesting to think where should the tailwind.config live. While you can argue that it's a frontend thing, it's also a build-time PostCSS thing, so I would think that the config file should live at the same level where you may have {nuxt,vite,postcss}.config. I feel (rc)config files are typically in root, and app is a Nuxt-app concept for pages, plugins, etc. There's also the .config proposal and we're definitely considering that so it should be even clearer, so feel free to chip into #808 and #790. 🙂
Now that Nuxt 4 is on the horizon, according to the new directory structure, should we move Tailwind config to the
app
folder, considering that Tailwind CSS is a frontend thing?The doc says this module looks for config file under the root path by default. Should this be changed as well? Or I have to update Nuxt config if I want to try out features of Nuxt 4:
The text was updated successfully, but these errors were encountered: