fix: adding support for testing projects that depend on Nuxt Layers

[JessicaSachs]

🔗 Linked issue

Resolves #1330

❓ Type of change

• 📖 Documentation (updates to the documentation or readme)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

Currently applications that use Nuxt Layers which have their own dependencies (/my-layer/node_modules) are not resolved. The search paths for the Nuxt project do not include the Layer for whatever reason. This differs from behavior when developing the application normally.

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@nuxt/test-utils@1329

commit: 43fab42

[JessicaSachs]

I was mistaken about the root cause of the issue I was getting with layers. All Vitest E2E tests are currently broken due to a regression introduced in Nuxt 3.16.0 when Nuxt adopted exsolve.

The fix for exsolve should be here unjs/exsolve#25 and Nuxt is targeting ^1.0.5 so once that fix is merged, Nuxt Vitest E2E should be working again for all users.

I'm going to close this PR, though I intend to create a new one in a bit to enable the E2E tests for this repository.