Skip to content

Conversation

@yamachi4416
Copy link
Contributor

@yamachi4416 yamachi4416 commented Dec 20, 2025

πŸ”— Linked issue

❓ 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

devtool now delegates config loading to startVitest instead of using the currently loaded viteConfig.

@pkg-pr-new
Copy link

pkg-pr-new bot commented Dec 20, 2025

Open in StackBlitz

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

commit: c74b2f5

@yamachi4416 yamachi4416 force-pushed the fix/devtool-vitest-ui-compatiblity branch from a81b759 to 744394a Compare December 21, 2025 10:30
noDiscovery: true,
},
test: {
dir: process.cwd(),
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

vitest fails with -r when this is specified
Example: pnpm vitest -r .\examples\app-vitest-full\

@yamachi4416 yamachi4416 force-pushed the fix/devtool-vitest-ui-compatiblity branch from 744394a to 639107e Compare December 21, 2025 12:28
@yamachi4416 yamachi4416 force-pushed the fix/devtool-vitest-ui-compatiblity branch from 639107e to c74b2f5 Compare December 21, 2025 15:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant