Skip to content

fix(config): browser setup in defineVitestProject#1724

Open
yamachi4416 wants to merge 3 commits into
nuxt:mainfrom
yamachi4416:fix-vitest-projects-browser-mode
Open

fix(config): browser setup in defineVitestProject#1724
yamachi4416 wants to merge 3 commits into
nuxt:mainfrom
yamachi4416:fix-vitest-projects-browser-mode

Conversation

@yamachi4416

@yamachi4416 yamachi4416 commented Jun 16, 2026

Copy link
Copy Markdown
Member

🔗 Linked issue

📚 Description

Fixed an issue where the browser mode setup was not executed if the environment was not specified as 'nuxt' in defineVitestProject

@socket-security

socket-security Bot commented Jun 16, 2026

Copy link
Copy Markdown

No dependency changes detected. Learn more about Socket for GitHub.

👍 No dependency changes detected in pull request

@pkg-pr-new

pkg-pr-new Bot commented Jun 16, 2026

Copy link
Copy Markdown

Open in StackBlitz

npm i https://pkg.pr.new/@nuxt/test-utils@1724
npm i https://pkg.pr.new/vitest-environment-nuxt@1724

commit: c6e40af

@yamachi4416 yamachi4416 force-pushed the fix-vitest-projects-browser-mode branch from 1bbac88 to 4b90de9 Compare June 16, 2026 15:18
@yamachi4416 yamachi4416 marked this pull request as ready for review June 16, 2026 15:31
@yamachi4416 yamachi4416 requested a review from danielroe as a code owner June 16, 2026 15:31
@coderabbitai

coderabbitai Bot commented Jun 16, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 1fd546d9-4dbe-4c61-92fd-23809dbe81fe

📥 Commits

Reviewing files that changed from the base of the PR and between 4b90de9 and c6e40af.

⛔ Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (1)
  • examples/app-vitest-workspace/package.json
🚧 Files skipped from review as they are similar to previous changes (1)
  • examples/app-vitest-workspace/package.json

📝 Walkthrough

Walkthrough

defineVitestProject in src/config.ts now pre-merges test.environment: 'nuxt' into the project config before calling resolveConfig, instead of mutating the resolved config afterward. The app-vitest-workspace example adds a Vitest browser project configuration scoped to *.browser.spec.ts, a browser test file that checks useAppConfig() and NuxtLink, and browser testing devDependencies in package.json.

Estimated code review effort: 3 (Moderate) | ~20 minutes

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly summarizes the main fix in defineVitestProject: browser setup behavior.
Description check ✅ Passed The description matches the change by explaining that browser mode setup was skipped unless the environment was nuxt.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@examples/app-vitest-workspace/app1/test/app.browser.spec.ts`:
- Around line 7-9: The assertion in the useAppConfig test block is checking for
exact key equality with toEqual(['nuxt']), which is brittle because it will fail
if any additional unrelated config keys are added. Instead of checking for exact
equality of all keys, change the expectation to use toContain('nuxt') to assert
only that the 'nuxt' key is present in the returned config object, making the
smoke test more resilient to future config additions.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 35d3e297-b4dd-4497-992c-2dd4d8f1484e

📥 Commits

Reviewing files that changed from the base of the PR and between e1a0f63 and 4b90de9.

⛔ Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (4)
  • examples/app-vitest-workspace/app1/test/app.browser.spec.ts
  • examples/app-vitest-workspace/app1/vitest.browser.config.ts
  • examples/app-vitest-workspace/package.json
  • src/config.ts

Comment thread examples/app-vitest-workspace/app1/test/app.browser.spec.ts
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.

2 participants