Better Nuxt/Astro integration

[tobiasdiez]

Description

Currently, it feels like vite-plus and nuxt/astro provide two different interfaces that don't talk to each other. In particular,

1. Nuxt/astro config cannot be used to specify vite+ config (see Use nuxt.config.ts / astro.config.mjs as Vite+ config for Nuxt/Astro #912)
2. vp dev and vp build don't call the correct nuxt/astro commands (see Running vp dev on a new Astro project doesn't work #1123)

(both issues were raised before but are now closed although they are not fixed)

Suggested solution

ad 1: create an offical vite+ nuxt/astro module that reads the vite+ config from nuxt/astro.config and exposes it in the temporary framework folder (eg .nuxt/viteplus.config.mjs), and in vite+ add a fallback to those known locations if a main vite.config is missing.

ad 2: recognize that the project is using nuxt/astro, and then call the correct framework commands

Alternative

No response

Additional context

No response

Validations

• Read the Contributing Guidelines.
• Confirm this request is for Vite+ itself and not for Vite, Vitest, tsdown, Rolldown, or Oxc.
• Check that there isn't already an issue requesting the same feature.

[Charles5277]

+1 — hitting the exact warning on a Nuxt 4 + Vite+ 0.1.14 project, and the previous discussion in #912 left a real gap that's worth re-surfacing.

The closing rationale in #912 ("if Nuxt wants to coexist with vite.config.ts, they should support export const nuxtConfig = … in it") puts the burden on Nuxt, but Nuxt's checkForExternalConfigurationFiles() has been there since 3.x and nuxt dev / nuxt build warn on every run regardless of file content. So as long as Vite+ requires a root vite.config.ts, every Nuxt+Vite+ user gets a permanent warning they can't silence.

What makes this hard to work around in our case specifically:

• The Vite+ docs already point users at .oxlintrc.* / .oxfmtrc.* as a fallback for vp lint / vp fmt, so those two commands aren't blocking.
• vp staged has no such fallback. vp staged --help says "using staged config from vite.config.ts", the migration guide explicitly says "only the staged config format is supported", and there's no --config flag. So we cannot keep vp staged (which is the recommended pre-commit entrypoint) without keeping a root vite.config.ts.
• Falling back to husky + lint-staged just to drop vite.config.ts defeats the point of adopting Vite+ as a unified toolchain.

Net effect: any project that follows Vite+'s recommended commit-hook setup and uses Nuxt is forced into a permanent warning loop with no ergonomic exit.

A few possible directions, in increasing order of invasiveness:

1. Accept a non-vite.config.* filename for vp staged only (e.g. --config flag, or auto-discover .viteplus/staged.ts). This sidesteps the Nuxt detector without committing to a full alternative-config scheme.
2. The official Nuxt module proposed in this issue's body — read Vite+ config from nuxt.config.ts and emit .nuxt/viteplus.config.mjs. Best long-term answer but biggest scope.
3. Coordinate with Nuxt to add an opt-in allowlist on the checkForExternalConfigurationFiles warning so users can declare "this vite.config.ts belongs to a non-Vite tool, please don't warn." Cheapest but requires upstream agreement on both sides.

Happy to file a separate vp staged --config issue if maintainers think that's a more tractable starting point than the full Nuxt-module proposal.