Skip to content

Conversation

@JessicaSachs
Copy link
Contributor

πŸ”— Linked issue

Resolves #1106

❓ 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

There was no example for Vitest Browser Mode. In order to get it working, I created an example, and then I had to make two code changes.

  • Changing the setup files from resolving to "entry.ts" vs "entry" may be due to a file path resolution issue?
  • Removing the [process.env.NODE_ENV] definition caused the process is not defined error to go away.

@JessicaSachs JessicaSachs requested a review from danielroe as a code owner May 2, 2025 22:03
@pkg-pr-new
Copy link

pkg-pr-new bot commented May 2, 2025

Open in StackBlitz

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

commit: 103876e

@danielroe danielroe changed the title fix: support Vitest Browser mode feat(config): support vitest browser mode May 3, 2025
Copy link
Member

@danielroe danielroe left a comment

Choose a reason for hiding this comment

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

Thank you ❀️

@danielroe danielroe merged commit 509a36d into nuxt:main May 3, 2025
6 checks passed
@github-actions github-actions bot mentioned this pull request May 1, 2025
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.

Support Vitest Browser Mode w/ Playwright provider

2 participants