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

未关闭
#1,883 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 2 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
25/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
nodejs, typescript

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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.

主要语言
TypeScript
星标
445
派生
121
平均合并
3 天 11 小时
30 天内合并 PR
23

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

nuxt/test-utils 的其他 Issue

查看 nuxt/test-utils 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。