Intermittent "#imports" package specifier error in Nuxt environment tests (monorepo/layer setup)

[Eschricht]

Environment

Operating system	Linux 6.8.0-100-generic
CPU	AMD Ryzen 7 7840HS with Radeon 780M Graphics (16 cores)
Node.js version	v24.11.1
nuxt/cli version	3.33.1
Package manager	pnpm@9.15.4
Nuxt version	4.3.1
Nitro version	2.13.1
Nuxt test-utils	4.0.0
Builder	vite@7.3.1
Config	-
Modules	-

Reproduction

https://github.com/Eschricht/nuxt-test-utils-monorepo

Describe the bug

I’m seeing intermittent import resolution failures when running Nuxt tests with @nuxt/test-utils in a monorepo reproduction.

Reproduction repo: https://github.com/Eschricht/nuxt-test-utils-monorepo

Environment

• @nuxt/test-utils: 4.0.0
• vitest: 4.0.18
• nuxt: 4.3.1
• pnpm: 9.15.4
• node: v24.11.1
• OS: Ubuntu Linux (kernel 6.8.0-100-generic)

Repro steps

pnpm install
pnpm test

Per the README, this can pass or fail depending on the run.
I reproduced this multiple times by looping pnpm test.

Expected behavior

All suites pass consistently.

Actual behavior

Intermittent failure with:

TypeError: Package import specifier "#imports" is not defined in package .../node_modules/@nuxtjs/color-mode/package.json
imported from .../node_modules/@nuxtjs/color-mode/dist/runtime/plugin.client.js

Example failing suite:

FAIL  |composable-nuxt| test/nuxt/composable.spec.ts

Repro frequency I observed

In one sample of 30 runs:

• pass: 9
• fail: 21

The failure signature was consistent (#imports in @nuxtjs/color-mode module).

Additional note

I also observed this failure in single-project mode:

pnpm vitest run --project composable-nuxt

So it may not be only cross-project Vitest concurrency.

Possible related issues

• Multiple nuxt environment projects collide if imported via vitest projects #1419

Additional context

No response

Logs

[coderabbitai]

🔗 Related PRs

#1516 - feat(runtime)!: change nuxt start timing to beforeAll hook [merged]
#1563 - fix(render): add missing nextTick import [merged]
#1564 - fix(runtime-utils): avoid local variable in mockNuxtImport macro [merged]
#1570 - fix(config): respect include options in non nuxt environment simple setup [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!