getVitestConfigFromNuxt returns empty viteConfig on Nuxt 4.6 + Vite 8 (rolldown) — nuxt environment tests fail with Missing "#app/..." specifier

Aperta
#1,883 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 2 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
25/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
nodejs, typescript

Direzione di ricerca

Start with getVitestConfigFromNuxt and startNuxtAndGetViteConfig in @nuxt/test-utils (config.mjs), which capture the config through the vite:configResolved hook. Run the repro script from the issue against a Nuxt 4.6 fixture to confirm the captured config is empty, then check how Nuxt's Vite 8 builder now exposes per-environment configs. Done when viteConfig.resolve.alias contains #app and #build, and a trivial nuxt environment test imports successfully.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Environment

  • Nuxt: 4.6.0
  • Vite: 8.3.4 (rolldown-vite)
  • Vitest: 4.1.11
  • @nuxt/test-utils: 4.3.4 (latest; also reproduced on 4.3.2)
  • Node: 22.23.4
  • OS: Linux

Description

On Nuxt 4.6 + Vite 8 (rolldown), getVitestConfigFromNuxt captures an empty object as the Vite config. As a result, #app/#build aliases and Nuxt's virtual-module plugins are never registered in the test Vite server, and every test file using the nuxt environment fails at import time:

Error: Missing "#app/composables/router" specifier in "@nuxt/test-utils" package
Plugin: vite:import-analysis

(#app/... falls through to package-imports resolution of @nuxt/test-utils because no alias matched.)

Minimal reproduction

// repro.mjs — run from any Nuxt 4.6 project root
const mod = await import('@nuxt/test-utils/dist/config.mjs')
const cfg = await mod.getVitestConfigFromNuxt(undefined, { overrides: { rootDir: process.cwd() } })
console.log('viteConfig keys:', Object.keys(cfg.viteConfig || {}))
console.log('resolve.alias present:', !!cfg.viteConfig?.resolve?.alias)

Expected: viteConfig contains Nuxt's client Vite config, including resolve.alias with #app, #build, ~, etc.

Actual:

viteConfig keys: []
resolve.alias present: false

Also reproduced with nitroEnvironment: true, and with both the app root and a minimal fixture (rootDir override). Reproduced with any trivial nuxt environment test file, e.g.:

// test/probe.test.ts
import { it } from 'vitest'
import { useNuxtApp } from '#app'

it('probe', () => { console.log(Object.keys(useNuxtApp())) })
// vitest.config.ts
import { defineVitestConfig } from '@nuxt/test-utils/config'
export default defineVitestConfig({ test: {} })

Analysis

getVitestConfigFromNuxt captures the config via the vite:configResolved hook (startNuxtAndGetViteConfig). With Nuxt 4.6's Vite 8 builder (@nuxt/vite-builder), the hook fires but the captured config has zero keys. Nuxt 4.6's builder now constructs per-environment configs (environments.client / environments.ssr, see vite-builder clientEnvironment() and the strippedConfig hook invocation in the build path), so the top-level Vite config shape test-utils expects appears to have moved.

Happy to provide more diagnostics if useful.

Lingua principale
TypeScript
Stelle
445
Fork
121
Merge medio
3g 11h
PR unite (30g)
23

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di nuxt/test-utils

Tutte le issue di nuxt/test-utils

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.