chore(deps): update dependency @repobuddy/vitest to v3

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@repobuddy/vitest (source)	^2.1.2 → ^3.0.0

---

Release Notes

repobuddy/repobuddy (@​repobuddy/vitest)

v3.0.1

Compare Source

Patch Changes

• Updated dependencies [fcd82e3]
  • @​repobuddy/test@1.1.2

v3.0.0

Compare Source

Major Changes

• 280e4b5: Support vitest 5 only.

  The vitest and @vitest/browser-playwright peer ranges move from ^4.0.15 to ^5.0.0.
  Stay on 2.x to keep using vitest 4.

Patch Changes

• 1620562: The readme no longer says every preset restores mocks (only browserTestPreset does), its load-test config no longer also runs the other tests, and its npm badges point at @repobuddy/vitest. The includeGeneralTests doc comment shows the right glob and no longer lists a .tsx file, which is a browser test, as a general test.
• Updated dependencies [1620562]
  • @​repobuddy/test@1.1.1

v2.4.1

Compare Source

Patch Changes

• 09c89a9: Run browserTestPreset() in the pre plugin phase.

  Vitest 5 sets up Browser Mode in a pre plugin that reads test.browser.enabled before normal plugins run.
  Without this, Vitest 5 fails with "The browser server was not initialized".

v2.4.0

Compare Source

Minor Changes

• 82b4815: Recognize *.load.ts|js as a test filename.

  Load tests are slow, so they are not part of a normal run. buddyConfigDefaults.include.testLoad
  holds their pattern, nodeTestPreset and browserTestPreset take an includeLoadTests option to
  opt in, and buddyConfigDefaults.exclude.test now covers .load. files so they are not counted as
  source in coverage.

v2.3.0

Compare Source

Minor Changes

• 628f3a8: Add expect.order, an AssertOrder factory for asserting code executes in the expected order.

  @repobuddy/test exports order, installOrder(), and the ExpectWithOrder type. installOrder(expect) adds order to any test runner's expect, so expect.order.plan(x) creates an AssertOrder planned for x steps.

  @repobuddy/vitest adds a @repobuddy/vitest/setup/order entry that installs it and augments vitest's ExpectStatic, so the only wiring needed is adding it to setupFiles.

Patch Changes

• Updated dependencies [628f3a8]
  • @​repobuddy/test@1.1.0

v2.2.0

Compare Source

Minor Changes

• 9492362: Recognise ts/ as a source directory.

  The include globs covered {src,source,code} while @repobuddy/jest has always
  resolved ['src', 'source', 'ts', 'js']. Most of these repos keep their sources in
  ts/, so the vitest presets matched nothing and every migration so far
  (resolve.imports, path-equal, just-func, fsa-emitter) hand-wrote a
  vitest.config.ts rather than importing the preset.

  js is deliberately not added. @repobuddy/jest picks the first existing
  directory from its list, whereas these are globs that union everything they match —
  so adding js risks pulling a build-output directory into the source set. No repo
  uses js/ as a source directory today.

v2.1.4

Compare Source

Patch Changes

• 5789ca2: Build with TypeScript 7.

  The emitted output changes cosmetically: TypeScript 7 preserves the source
  quote style in re-export specifiers (export * from './x.js' rather than
  "./x.js"), and the property order inside one inferred .d.ts union in
  @repobuddy/typescript differs. No public API, type or runtime behavior
  changes.

  The tsconfig presets themselves are unchanged and remain valid under both
  TypeScript 6 and 7 — they use no option TypeScript 7 removed, and
  @repobuddy/typescript now type-checks and builds against 7.0.2 using them.

• Updated dependencies [5789ca2]

  • @​repobuddy/test@1.0.2

v2.1.3

Compare Source

Patch Changes

• 8047432: Annotate browserTestPreset() and nodeTestPreset() return types as vite's Plugin.

  The return types were inferred structurally, so the emitted .d.ts leaked the whole config shape.
  test.browser.instances[].browser is typed against vitest's augmentable _BrowserNames interface,
  which resolved to string when the presets were built without a browser provider installed. In a
  consumer project @vitest/browser-playwright augments _BrowserNames, browser narrows to the
  provider's union, and string is no longer assignable — browserTestPreset() failed with TS2769
  "No overload matches this call".

  Annotating the return type keeps the emitted types independent of what is installed at build time.
  Runtime behavior is unchanged.

  Fixes #​610

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 41b332c

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (352d402) to head (41b332c).

Additional details and impacted files

@@            Coverage Diff            @@
##              main      #300   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            1         1           
  Lines            2         2           
=========================================
  Hits             2         2           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[mergify]

Tick the box to add this pull request to the merge queue (same as @mergifyio queue).

• Queue this pull request