More obvious deprecation of Nuxt 2 settings in nuxt.config.js

[manniL]

Describe the feature

Hey 👋🏻

right now, it seems difficult for several people to realize which config options from nuxt.config.js/nuxt.config.ts are actually used in Nuxt 3 (e.g. target). Right now, the only hint is the @version tag in the JSDocs which isn't very prominent though.

It'd be nice to have a better alternative (e.g. @deprecated?) so people can be more aware.

Additional information

• Would you be willing to help implement this feature?
• Could this feature be implemented as a module?

Final checks

• Read the contribution guide.
• Check existing discussions and issues.

[danielroe]

This is absolutely planned, though I couldn't find an issue for it.

[manniL]

though I couldn't find an issue for it.

I think this is usually a "side effect" in other Nuxt3 issues, e.g.:

• [RC 10] "nuxt generate" not logging errors #14957
• console errors occur when build with no-ssr mode #14908
• Can't change SPA Fallback from 200.html to 404.html #15056
• Basically any issue where "target: static" is included 🙈 (query)

But given the amount of people writing target in their Nuxt3 config, I assume that there is a good potential for improving DX 😋

[pi0]

Thanks for making issue @manniL. Indeed we need to move Nuxt 2 types to bridge and mark them as never for 3+ schema to avoid accidentally using them. I had planned to work on this soon.