Skip to content
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

Change default config file location for Nuxt 4? #862

Closed
AnotiaWang opened this issue Jun 15, 2024 · 1 comment
Closed

Change default config file location for Nuxt 4? #862

AnotiaWang opened this issue Jun 15, 2024 · 1 comment
Labels
question Further information is requested

Comments

@AnotiaWang
Copy link

AnotiaWang commented Jun 15, 2024

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:

export default defineNuxtConfig({
  // ...
  future: {
    compatibilityVersion: 4
  },
  tailwindcss: {
    configPath: './app/tailwind.config'
  },
})
@AnotiaWang AnotiaWang added the question Further information is requested label Jun 15, 2024
@ineshbose
Copy link
Collaborator

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. 🙂

@ineshbose ineshbose closed this as not planned Won't fix, can't repro, duplicate, stale Jun 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants