e2e setup() leaves its random .nuxt/test/<id> build directory behind after every run

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

维护者通常 2 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
76/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
活跃
技术栈
node.js, nuxt, typescript
领域
testing

调研方向

The issue points to loadFixture in the generated dist/e2e-*.mjs and shows the cleanup registration condition. Trace this code to its source and check how loadNuxt() creates the build directory and how teardown runs. Reproduce with the provided Vitest e2e test; done when the test-created random build directory is removed after the test finishes.

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

描述

Environment
  • @nuxt/test-utils 4.1.0, nuxt 4.5.2, Node 22.21.1, macOS
What happens

Every run of an e2e test that uses setup({ server: true }) (build mode, no buildDir option) leaves its random build directory, .nuxt/test/<randomId> (about 23 MB for our app), behind after the run finishes. They pile up, one per run.

Why

In loadFixture (dist/e2e-*.mjs), the teardown that removes the build directory is only registered when the directory does not exist after loadNuxt():

ctx.nuxt = await loadNuxt({ ... overrides: ctx.options.nuxtConfig ... })
const buildDir = ctx.nuxt.options.buildDir
if (!existsSync(buildDir)) {
  await promises.mkdir(buildDir, { recursive: true })
  ctx.teardown = ctx.teardown || []
  ctx.teardown.push(() => promises.rm(buildDir, { recursive: true, force: true }))
}

On our app loadNuxt() has already created the directory by that point, so the cleanup is never registered.

Steps to reproduce
  1. In a Nuxt 4 app, add a test:
    // @vitest-environment node
    import { expect, it } from "vitest";
    import { fetch, setup } from "@nuxt/test-utils/e2e";
    await setup({ server: true, browser: false });
    it("serves /", async () => { expect((await fetch("/")).status).toBe(200); });
    
  2. Run it with npx vitest run <file>; it passes.
  3. ls .nuxt/test shows a <randomId> directory left behind. Each further run adds another.
Expected

The build directory created for the test is removed when the test finishes.

主要语言
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 摘要。