-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Document that user should not use separate nitro.config.ts
(and other configs like webpack/vitest/...)
#15085
Comments
As discussed in nuxt/framework#8683 we can improve Nitro docs to guide Nuxt users. It wouldn't hurt to also add a |
nitro.config.ts
nitro.config.ts
(and other configs like webpack/vitest/...)
I think we might be able to close this as completed in #22521. What do you think? We can also add to docs... |
I think the warning is enough to close this. Nice idea for docs it can be an appendix in here to help users onboard in next steps if they see any (external) docs referring to |
Totally fine - that's what I was suggesting back then too 😂 Happy to see it landed 👍🏻 |
Describe the feature
When using Nuxt, the nitro config should live inside the
nuxt.config.{js,ts}
instead of a separatenitro.config.{js,ts}
. Same for a custom webpack or vite config. Ideally this should be documented.Additional information
Final checks
The text was updated successfully, but these errors were encountered: