vite-plus 0.3.3 → 1.0.0-rc.1

package/docs/guide/vitest-v5.md

@@ -0,0 +1,221 @@
+# Upgrade to Vitest 5
+
+Vite+ bundles Vitest `5.0.1`. Use Node `^22.18.0 || ^24.11.0 || >=26.0.0` for the CLI and tests.
+
+## Before you migrate
+
+Run `vp migrate` from the workspace root before updating dependencies by hand. Keep the original lockfile and installed packages available so the migration can identify the source Vitest version, including the runner inside an older `vite-plus` installation.
+
+Upgrade projects older than Vitest 4 to v4 before running this migration. If the original version cannot be determined, restore and install the original lockfile, then rerun `vp migrate`.
+
+```bash
+vp migrate
+vp install
+vp check
+vp test
+```
+
+Read the file-specific review report before committing the result. The migration stops before dependency updates for conflicting `test.api` and `test.browser.api` settings or removed runtime APIs without a supported replacement. Resolve these blockers and run the command again. You can finish safe edits with a successful exit status while review items remain.
+
+You can keep equivalent static `test.api` and `test.browser.api` values, including objects with different property order or quote styles. The migration removes the redundant `browser.api`. Choose one configuration for conflicting values or expressions that need evaluation; v5 uses one API server.
+
+## Node runtime
+
+The migration upgrades incompatible runtime pins to the nearest supported minimum before installing dependencies. For example, `20.19.0` becomes `22.18.0`, `24.10.0` becomes `24.11.0`, and `25.9.0` becomes `26.0.0`. Supported pins stay unchanged. Unresolved selectors still need review.
+
+Keep your library's public `engines.node` contract separate from its test runtime. The migration does not change that contract. You do not need to review an engine range with a supported minimum, such as `>=22.19.0`, or a whole supported major, such as `24.x`. Use a concrete runtime pin at or above the supported minimum for that major.
+
+The Node compatibility checks cover `.node-version`, `.nvmrc`, and the `engines.node`, `devEngines.runtime`, and `volta.node` declarations in `package.json`. Node versions in CI workflows, containers, and other files are outside the scope of these checks.
+
+## Preserve existing behavior
+
+Preview builds link to the PR documentation site for Vite+ guidance. Release builds use `viteplus.dev`. Links to upstream Vitest documentation stay the same.
+
+For v4 configs, the migration adds compatibility settings where you omitted the corresponding option. Explicit settings take precedence. Beside each added setting, you get a comment with the reason, guidance for adopting v5 behavior, and links to the cleanup checklist and the Vitest migration guide:
+
+```ts
+test: {
+  // Vitest v4 compatibility: preserve mock call history.
+  // Remove after tests no longer rely on calls from setup or earlier tests.
+  // https://viteplus.dev/guide/vitest-v5#remove-unneeded-compatibility-settings
+  // https://vitest.dev/guide/migration/#clearmocks-is-enabled-by-default
+  clearMocks: false,
+}
+```
+
+| Added setting                                                                                                               | Behavior to check before removing it                                                                                                    |
+| --------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
+| [`test.clearMocks: false`](https://vitest.dev/guide/migration/#clearmocks-is-enabled-by-default)                            | Check assertions that depend on mock calls from setup, `beforeAll`, or earlier tests. V5 clears that history before each test.          |
+| [`test.sharedViteServer: false`](https://vitest.dev/guide/migration/#inline-projects-share-the-vite-server-by-default)      | Check plugins and config hooks with a shared server. V5 initializes them once for eligible inline projects.                             |
+| [Inline `extends: false`](https://vitest.dev/guide/migration/#inline-projects-inherit-the-root-config-by-default)           | Check inherited root options, plugins, and setup files. V5 merges arrays, so avoid duplicate setup.                                     |
+| [`browser.locators.exact: false`](https://vitest.dev/guide/migration/#locators-are-strict-by-default)                       | Update locators for full, case-sensitive matches, or opt out on individual locators.                                                    |
+| [Glob threshold `perFile: true`](https://vitest.dev/guide/migration/#glob-coverage-thresholds-no-longer-inherit-perfile)    | Keep for per-file coverage enforcement. Remove to check matching files as a group.                                                      |
+| [`fakeTimers.toNotFake: ['Temporal']`](https://vitest.dev/guide/migration/#fake-timers-and-setsystemtime-now-mock-temporal) | Check tests that use the global Temporal polyfill with fake timers. Remove only `Temporal` to use mocked time; retain other exclusions. |
+
+New projects use v5 defaults. You may be able to remove some generated compatibility settings with no code changes or small, localized fixes. Follow the checks below before removing them. These options remain supported in v5; keep compatibility for now if removal requires extensive test changes.
+
+The migration leaves your existing settings and comments untouched. It does not add comments to settings from an earlier migration, since it cannot distinguish those settings from your own choices. Repeated runs do not duplicate comments or restore comments you removed.
+
+If your project has no test config, you can use the v5 defaults without a review prompt or a new compatibility config. Other migration steps, such as merging lint configuration, can create `vite.config.ts`; the v4 compatibility settings apply to that new config during the same migration.
+
+After upgrading to v5, you can rerun `vp migrate` without reapplying v4 compatibility defaults, including in projects without a config. Finish the dependency installation before rerunning migration.
+
+Resolve or save the first run's review report before discarding the original dependencies. Later runs use the current Vitest version and files, so they might not repeat reviews that depended on the original v4 behavior.
+
+### Remove unneeded compatibility settings
+
+First, validate the migrated project with its compatibility settings intact. Then use the migration diff and the `Vitest v4 compatibility` comments to identify additions in root, workspace, and inline project configs. Leave pre-existing user settings and settings with an unclear origin unchanged.
+
+Remove one added setting at a time. Check which value the project uses after removal, including inherited options, plugins, and setup files. First run the affected suites without code changes. Include browser and coverage runs where relevant; a passing Node suite does not validate browser locators. For `fakeTimers.toNotFake`, remove only the added `Temporal` entry and retain other exclusions.
+
+You can make small, localized application, test, or setup fixes that preserve test intent, such as correcting a locator or adjusting mock setup in a few tests. Keep assertions and test coverage intact, and review any snapshot changes. If removal requires widespread test edits or shared setup refactoring, keep compatibility for now and record the follow-up work.
+
+Keep a removal if the affected tests pass, run the same test set without new skips, and support the resulting behavior. Remove its generated comment too. Restore the setting and comment if validation still fails, required suites cannot run, or the result remains uncertain. Undo only cleanup-specific trial edits; preserve completed migration fixes and unrelated work. Distinguish a deferred rewrite from a setting you could not validate.
+
+Passing tests do not prove that coverage enforcement is unchanged. Keep generated glob-threshold `perFile: true` settings unless you intend to switch from per-file thresholds to aggregate checking. An agent should request your approval for that change. See [Vitest's coverage threshold migration](https://vitest.dev/guide/migration/#glob-coverage-thresholds-no-longer-inherit-perfile).
+
+After the individual checks, run the full validation suite with the accepted removals together. Report the config path, removal decision, code changes, validation commands and results, and any remaining work for each candidate. If you retain an option as a project choice, replace its compatibility comment with that reason.
+
+## Source changes
+
+The migration uses syntax and import bindings for targeted edits. You get a review item for dynamic options, ambiguous wrappers, or a callback whose contract cannot accept `async`.
+
+```ts
+// Before
+test.sequential('result', () => {
+  expect(result).resolves.toBe(42);
+});
+
+// After
+test('result', { concurrent: false }, async () => {
+  await expect(result).resolves.toBe(42);
+});
+```
+
+In browser tests, use `toMatchTextContent` for v4 string and regular-expression assertions. The v4 string matcher accepted partial text, so identical text in a fixture does not prove that you intended v5's exact match. Choose `toHaveTextContent` yourself if you want the new semantics.
+
+Keep Node `@testing-library/jest-dom` assertions unchanged. In a mixed Node/browser package, the migration checks static project membership before renaming a matcher. You must review shared files, dynamic configs, and command-line browser overrides. Calls through `expect.element()` identify browser assertions without that ambiguity.
+
+Await `render` from `vitest-browser-vue` and `vitest-browser-svelte` before querying its result. Replace `toThrow('')` and `toThrowError('')` with `/^$/` to keep assertions for an empty message.
+
+For programmatic config loading, replace `{ viteConfig, vitestConfig }` destructuring with the return value from `resolveConfig()` and its `.test` property. Direct migrated `vitest list` commands get `--no-static-parse`; supported `Vitest.collect(filters, options)` calls get `{ staticParse: false }`. Keep an explicit static-parse choice if you want v5's static collection.
+
+## Benchmarks
+
+Use direct `bench` calls with inline, zero-argument callbacks or references to unchanged local functions. You can use dynamic names; the migration captures them once during registration. It preserves the workload callback and runs it through the v5 `bench` fixture inside a test. Simple `bench.skip`, `bench.only`, and `bench.todo` calls become the corresponding test modifiers. Calls inside ordinary `describe` and `suite` callbacks retain their surrounding scopes.
+
+```ts
+// Before
+import { bench } from 'vitest';
+bench('parse', () => JSON.parse('{"value":1}'));
+
+// After
+import { test } from 'vitest';
+test('parse', async ({ bench }) => {
+  await bench('parse', () => JSON.parse('{"value":1}')).run();
+});
+```
+
+Keep benchmark files matched by `benchmark.include`. The `vitest bench` and `vp test bench` commands remain supported. The migration does not remove them.
+
+You can migrate built-in `benchmark.reporters` settings (`default` and `verbose`) and literal `benchmark.outputFile` or `benchmark.outputJson` paths to top-level reporters. Existing reporter destinations take precedence over a proposed move: resolve conflicting paths, terminal reporter choices, and JSON stdout consumers by hand. Project-specific settings, config merges, and custom or dynamic reporters also need review. In v5, regular tests and benchmarks share reporters.
+
+For a literal command such as `vitest bench --outputJson=bench.json`, the migration selects the JSON reporter and keeps the file path. The v5 JSON report contains test results with per-test benchmarks. If you consume these reports outside Vitest, update readers that expect the v4 format.
+
+Review calls with benchmark options, imported or reassigned callbacks, callback parameters, or wrappers. Baseline `compare` settings and `--compare` flags remain blockers. Set up per-benchmark result storage and an explicit comparison inside a test. See the [Vitest benchmark migration guide](https://vitest.dev/guide/migration/#benchmarking-api-rewrite) and [benchmarking guide](https://vitest.dev/guide/benchmarking) for replacements. Use `bench.compare()` if you need a comparison table across several workloads.
+
+## Entry points and packages
+
+Use `vite-plus/test` for assertions and supported runner APIs. Keep coverage providers and `@vitest/ui` at the bundled runner's exact version, `5.0.1`. Keep `@vitest/web-worker` aligned when your project uses it.
+
+| v4 import                                | v5 import or action                                                         |
+| ---------------------------------------- | --------------------------------------------------------------------------- |
+| `vitest/coverage`, `vitest/reporters`    | `vite-plus/test/node`                                                       |
+| `vitest/environments`, `vitest/snapshot` | `vite-plus/test/runtime`                                                    |
+| `vitest/mocker`                          | `vite-plus/test/mocker`                                                     |
+| `vitest/runners`, `vitest/suite`         | Review `TestRunner` and its static methods from `vite-plus/test`.           |
+| Root-compatible `@vitest/expect` symbols | `vite-plus/test`; review unsupported helpers.                               |
+| `@vitest/runner`                         | Migrate supported symbols to the root API and review the remaining imports. |
+| `vitest/internal/module-runner`          | Redesign the integration; no public replacement exists.                     |
+| `@vitest/ws-client`                      | Retain if needed; upstream no longer adds v5 features.                      |
+
+Vite+ 1.0 removes `vite-plus/test/coverage`, `/reporters`, `/environments`, and `/snapshot`. Run `vp migrate` to rewrite these existing Vite+ imports to the same `node` or `runtime` entries shown above. Vite+ retains `vite-plus/test/mocker` for the standalone `@vitest/mocker` API. It does not provide partial runner or expect plugin shims.
+
+## Community WebDriverIO provider
+
+Vite+ 1.0 removes the `vite-plus/test/browser-webdriverio` exports. Use `@vitest/browser-webdriverio` and choose a provider version and framework peers that support your tests. The community maintains this package on its own release schedule.
+
+`vp migrate` changes legacy provider imports to `@vitest/browser-webdriverio` and ensures a provider version of at least `5.0.0`. It adds `^5.0.0` when the provider is missing, upgrades older versions, and narrows ranges that still allow v4. It also updates referenced catalog entries and removes overrides that force an older provider. Versions and ranges already above this minimum stay unchanged. The migration ensures the required `webdriverio` peer is installed without upgrading an existing framework version.
+
+For projects that use this provider, `vp migrate` adds an `@vitest/browser` override that matches the bundled Vitest version. Yarn uses `resolutions`. This prevents the provider's version range from retaining an older browser package in the lockfile.
+
+You manage provider upgrades after this migration; Vite+ does not synchronize community releases with Vitest. Existing imports from the community package stay unchanged. For custom dependencies that the migrator cannot verify, resolve the diagnostic before retrying migration. See the [upstream package migration guide](https://vitest.dev/guide/migration/#package-migration).
+
+Legacy Vite+ WebDriverIO `/context` imports move to `vite-plus/test/browser/context`. Keep runtime browser APIs on this shared entry; the community provider's `/context` entry contains types only.
+
+The optional peer declaration still follows Vitest's dependency metadata. It does not provide a Vite+ export or synchronize provider releases.
+
+## Reports and screenshots
+
+The migration does not edit or report changes that affect only title formatting, report output, artifact paths, or dependency deprecation. It leaves regular reporter settings unchanged and does not add `stdout: true`. Removed benchmark APIs and flags still need migration so commands can run.
+
+If you consume generated reports or artifacts outside Vitest, check these paths. Keep old ignore entries while files remain in those directories. The migration adds `.vitest/` to `.gitignore` without deleting old entries.
+
+| Output              | v4 default                    | v5 default                                 |
+| ------------------- | ----------------------------- | ------------------------------------------ |
+| Attachments         | `.vitest-attachements/`       | `.vitest/attachments/`                     |
+| Failure screenshots | `__screenshots__/`            | `.vitest/attachments/failure-screenshots/` |
+| Blob reports        | `.vitest-reports/blob-*.json` | `.vitest/blob/blob-*.json`                 |
+| HTML                | `html/index.html`             | `.vitest/index.html`                       |
+| JSON                | stdout                        | `.vitest/json/output.json`                 |
+| JUnit               | stdout                        | `.vitest/junit/output.xml`                 |
+
+HTML reporter options now use `outputDir` instead of the file-valued `outputFile`. Set `outputDir` yourself if you need a custom destination. Other reporters retain `outputFile` support. See the [upstream report changes](https://vitest.dev/guide/migration/#generated-reports-and-artifacts-use-the-vitest-directory).
+
+Copy a custom `browser.screenshotDirectory` to `browser.expect.toMatchScreenshot.screenshotDirectory`. Review reference images before moving or regenerating them; v4 could save them in an unintended location. The default reference screenshot directory remains `__screenshots__`.
+
+## Resolve migration findings
+
+Each Vitest v5 `BLOCK` or `REVIEW` item includes a `Docs` link. Follow the link for the relevant API change or migration rule. A blocker stops dependency updates; a review item requires you to check the result but does not stop safe edits.
+
+For dynamic configs or shared files, determine the effective Vitest project settings before editing. Resolve config functions, spreads, and external inheritance, or make the compatibility changes by hand. Confirm which runner owns unimported globals in a mixed-runner project.
+
+For parser failures or overlapping edits, keep the original file and apply the documented change by hand. Run `vp migrate` again after resolving the issue. A successful exit can still include review items; keep that report until you finish the manual changes.
+
+## Review checklist
+
+Use the file locations in the migration report to review these changes. Run browser and coverage suites as well as Node tests.
+
+For jest-dom matcher types, load `@testing-library/jest-dom/vitest` in `compilerOptions.types` or import it from a TypeScript setup file that your `tsconfig.json` includes. The root `@testing-library/jest-dom` type entry augments Jest. A JavaScript setup file excluded by `allowJs: false` does not load the Vitest augmentation for type checking. Review shared Jest/Vitest configs before changing their type entries.
+
+With `vitest@5.0.1`, loading browser declarations first can also make TypeScript reject valid Node jest-dom assertions: `toHaveTextContent(/pattern/)` and CSS custom properties in `toHaveStyle()`. We reproduced this conflict with upstream imports and with Vite+ imports. Both `@testing-library/jest-dom@6.9.1` and `7.0.1` reproduce it. Check the declarations loaded by each test `tsconfig.json`; adding the jest-dom type entry alone might not resolve the conflict. Keep the affected project on the v4-based release until its Node and browser matcher types pass separate checks.
+
+| Area                  | Required review                                                                                                                                                                            |
+| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| Test selection        | Full names use `>` separators. Check name filters that span suite boundaries; plain single-segment filters do not need review.                                                             |
+| Hoisted mocks         | Move nested `vi.mock`, `vi.unmock`, and `vi.hoisted` calls to the top level after checking captured variables.                                                                             |
+| Browser automocks     | Factory-free mocks retain mock defaults. Choose `{ spy: true }` if you need real implementations.                                                                                          |
+| Constructor mocks     | Check prototypes, methods, and `instanceof` for `vi.fn`, `vi.spyOn`, and `mockImplementation`.                                                                                             |
+| Benchmarks            | Review benchmark calls that the migration could not convert, comparison groups, and removed reporting options. Keep supported options such as `benchmark.enabled` and `benchmark.include`. |
+| Async assertions      | Await or return `resolves`, `rejects`, file snapshots, polls, and browser assertions. Review `expect.poll` timeouts without increasing them to hide failures.                              |
+| Matcher types         | Update old `Assertion<T>`, `Matchers<T>`, and `jest.Matchers` declarations for return and received type parameters.                                                                        |
+| Browser commands      | Accept `SerializedLocator` objects instead of selector strings.                                                                                                                            |
+| Browser UI            | Use Vitest's printed URLs, including UI tokens and orchestrator `sessionId`. Check headed/headless screenshots at fixed viewports.                                                         |
+| Project configuration | Check dynamic projects, root-config merges, nested projects, and hooks that assume one server or config execution per project.                                                             |
+| Test collection       | Review dynamic command wrappers and programmatic `collect()` calls whose static-parse options need manual edits.                                                                           |
+| Coverage              | Compare v4/v5 resolved file sets for configured `coverage.include` and `coverage.exclude`. Relative-path matching can change the measured set.                                             |
+| Worker IDs            | Review arithmetic and indexing based on `VITEST_POOL_ID` or `VITEST_WORKER_ID`; IDs start at 1.                                                                                            |
+| Custom environments   | Restore `populateGlobal().originals` entries with `Object.defineProperty`; the map contains descriptors.                                                                                   |
+| DOM globals           | Check assignments in jsdom/happy-dom tests; global assignments also update the window.                                                                                                     |
+| Temporal              | Review scopes that use Temporal and `vi.setSystemTime()`. `toNotFake` does not preserve behavior without fake timers.                                                                      |
+| Removed APIs          | Replace unsupported runner and internal imports before updating packages. Type-only references still require review and type checks.                                                       |
+
+## Run below a config directory
+
+Vitest v5 no longer searches parent directories for a config. From a subdirectory, pass both the parent config and the intended test directory:
+
+```bash
+vp test --config ../vite.config.ts --dir .
+```
+
+See the [upstream Vitest 5 migration guide](https://vitest.dev/guide/migration/) for API examples and the new benchmark design.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "vite-plus",
-  "version": "0.3.3",
+  "version": "1.0.0-rc.1",
   "description": "The Unified Toolchain for the Web",
   "homepage": "https://viteplus.dev/guide",
   "bugs": {
@@ -14,8 +14,6 @@
     "directory": "packages/cli"
   },
   "bin": {
-    "oxfmt": "./bin/oxfmt",
-    "oxlint": "./bin/oxlint",
     "vp": "./bin/vp",
     "vpr": "./bin/vpr"
   },
@@ -141,35 +139,14 @@
       "types": "./dist/test/internal/browser.d.ts",
       "default": "./dist/test/internal/browser.js"
     },
-    "./test/runners": {
-      "types": "./dist/test/runners.d.ts",
-      "default": "./dist/test/runners.js"
-    },
-    "./test/suite": {
-      "types": "./dist/test/suite.d.ts",
-      "default": "./dist/test/suite.js"
-    },
-    "./test/environments": {
-      "types": "./dist/test/environments.d.ts",
-      "default": "./dist/test/environments.js"
+    "./test/internal/traces": {
+      "default": "./dist/test/internal/traces.js"
     },
     "./test/config": {
       "types": "./dist/test/config.d.ts",
       "require": "./dist/test/config.cjs",
       "default": "./dist/test/config.js"
     },
-    "./test/coverage": {
-      "types": "./dist/test/coverage.d.ts",
-      "default": "./dist/test/coverage.js"
-    },
-    "./test/reporters": {
-      "types": "./dist/test/reporters.d.ts",
-      "default": "./dist/test/reporters.js"
-    },
-    "./test/snapshot": {
-      "types": "./dist/test/snapshot.d.ts",
-      "default": "./dist/test/snapshot.js"
-    },
     "./test/runtime": {
       "types": "./dist/test/runtime.d.ts",
       "default": "./dist/test/runtime.js"
@@ -178,6 +155,10 @@
       "types": "./dist/test/worker.d.ts",
       "default": "./dist/test/worker.js"
     },
+    "./test/mocker": {
+      "types": "./dist/test/mocker.d.ts",
+      "default": "./dist/test/mocker.js"
+    },
     "./test/browser-playwright": {
       "types": "./dist/test/browser-playwright.d.ts",
       "default": "./dist/test/browser-playwright.js"
@@ -210,22 +191,6 @@
       "types": "./dist/test/browser/providers/preview/context.d.ts",
       "default": "./dist/test/browser/providers/preview/context.js"
     },
-    "./test/browser-webdriverio": {
-      "types": "./dist/test/browser-webdriverio.d.ts",
-      "default": "./dist/test/browser-webdriverio.js"
-    },
-    "./test/browser/providers/webdriverio": {
-      "types": "./dist/test/browser/providers/webdriverio.d.ts",
-      "default": "./dist/test/browser/providers/webdriverio.js"
-    },
-    "./test/browser-webdriverio/context": {
-      "types": "./dist/test/browser-webdriverio/context.d.ts",
-      "default": "./dist/test/browser-webdriverio/context.js"
-    },
-    "./test/browser/providers/webdriverio/context": {
-      "types": "./dist/test/browser/providers/webdriverio/context.d.ts",
-      "default": "./dist/test/browser/providers/webdriverio/context.js"
-    },
     "./test/browser/context": {
       "types": "./dist/test/browser/context.d.ts",
       "default": "./dist/test/browser/context.js"
@@ -252,129 +217,141 @@
       "types": "./dist/test/browser-compat.d.ts",
       "default": "./dist/test/browser-compat.js"
     },
-    "./test/plugins/runner": {
-      "default": "./dist/test/plugins/runner.js"
-    },
-    "./test/plugins/runner-utils": {
-      "default": "./dist/test/plugins/runner-utils.js"
-    },
-    "./test/plugins/runner-types": {
-      "default": "./dist/test/plugins/runner-types.js"
-    },
     "./test/plugins/utils": {
+      "types": "./dist/test/plugins/utils.d.ts",
       "default": "./dist/test/plugins/utils.js"
     },
     "./test/plugins/utils-source-map": {
+      "types": "./dist/test/plugins/utils-source-map.d.ts",
       "default": "./dist/test/plugins/utils-source-map.js"
     },
     "./test/plugins/utils-source-map-node": {
+      "types": "./dist/test/plugins/utils-source-map-node.d.ts",
       "default": "./dist/test/plugins/utils-source-map-node.js"
     },
     "./test/plugins/utils-error": {
+      "types": "./dist/test/plugins/utils-error.d.ts",
       "default": "./dist/test/plugins/utils-error.js"
     },
     "./test/plugins/utils-helpers": {
+      "types": "./dist/test/plugins/utils-helpers.d.ts",
       "default": "./dist/test/plugins/utils-helpers.js"
     },
     "./test/plugins/utils-display": {
+      "types": "./dist/test/plugins/utils-display.d.ts",
       "default": "./dist/test/plugins/utils-display.js"
     },
     "./test/plugins/utils-timers": {
+      "types": "./dist/test/plugins/utils-timers.d.ts",
       "default": "./dist/test/plugins/utils-timers.js"
     },
     "./test/plugins/utils-offset": {
+      "types": "./dist/test/plugins/utils-offset.d.ts",
       "default": "./dist/test/plugins/utils-offset.js"
     },
     "./test/plugins/utils-resolver": {
+      "types": "./dist/test/plugins/utils-resolver.d.ts",
       "default": "./dist/test/plugins/utils-resolver.js"
     },
     "./test/plugins/utils-serialize": {
+      "types": "./dist/test/plugins/utils-serialize.d.ts",
       "default": "./dist/test/plugins/utils-serialize.js"
     },
     "./test/plugins/utils-constants": {
+      "types": "./dist/test/plugins/utils-constants.d.ts",
       "default": "./dist/test/plugins/utils-constants.js"
     },
     "./test/plugins/utils-diff": {
+      "types": "./dist/test/plugins/utils-diff.d.ts",
       "default": "./dist/test/plugins/utils-diff.js"
     },
     "./test/plugins/spy": {
+      "types": "./dist/test/plugins/spy.d.ts",
       "default": "./dist/test/plugins/spy.js"
     },
-    "./test/plugins/expect": {
-      "default": "./dist/test/plugins/expect.js"
-    },
     "./test/plugins/snapshot": {
+      "types": "./dist/test/plugins/snapshot.d.ts",
       "default": "./dist/test/plugins/snapshot.js"
     },
     "./test/plugins/snapshot-environment": {
+      "types": "./dist/test/plugins/snapshot-environment.d.ts",
       "default": "./dist/test/plugins/snapshot-environment.js"
     },
     "./test/plugins/snapshot-manager": {
+      "types": "./dist/test/plugins/snapshot-manager.d.ts",
       "default": "./dist/test/plugins/snapshot-manager.js"
     },
     "./test/plugins/mocker": {
+      "types": "./dist/test/plugins/mocker.d.ts",
       "default": "./dist/test/plugins/mocker.js"
     },
     "./test/plugins/mocker-node": {
+      "types": "./dist/test/plugins/mocker-node.d.ts",
       "default": "./dist/test/plugins/mocker-node.js"
     },
     "./test/plugins/mocker-browser": {
+      "types": "./dist/test/plugins/mocker-browser.d.ts",
       "default": "./dist/test/plugins/mocker-browser.js"
     },
     "./test/plugins/mocker-redirect": {
+      "types": "./dist/test/plugins/mocker-redirect.d.ts",
       "default": "./dist/test/plugins/mocker-redirect.js"
     },
     "./test/plugins/mocker-transforms": {
+      "types": "./dist/test/plugins/mocker-transforms.d.ts",
       "default": "./dist/test/plugins/mocker-transforms.js"
     },
     "./test/plugins/mocker-automock": {
+      "types": "./dist/test/plugins/mocker-automock.d.ts",
       "default": "./dist/test/plugins/mocker-automock.js"
     },
     "./test/plugins/mocker-register": {
+      "types": "./dist/test/plugins/mocker-register.d.ts",
       "default": "./dist/test/plugins/mocker-register.js"
     },
     "./test/plugins/pretty-format": {
+      "types": "./dist/test/plugins/pretty-format.d.ts",
       "default": "./dist/test/plugins/pretty-format.js"
     },
     "./test/plugins/browser": {
+      "types": "./dist/test/plugins/browser.d.ts",
       "default": "./dist/test/plugins/browser.js"
     },
     "./test/plugins/browser-context": {
+      "types": "./dist/test/plugins/browser-context.d.ts",
       "default": "./dist/test/plugins/browser-context.js"
     },
     "./test/plugins/browser-client": {
       "default": "./dist/test/plugins/browser-client.js"
     },
     "./test/plugins/browser-locators": {
+      "types": "./dist/test/plugins/browser-locators.d.ts",
       "default": "./dist/test/plugins/browser-locators.js"
     },
     "./test/plugins/browser-playwright": {
+      "types": "./dist/test/plugins/browser-playwright.d.ts",
       "default": "./dist/test/plugins/browser-playwright.js"
     },
-    "./test/plugins/browser-webdriverio": {
-      "default": "./dist/test/plugins/browser-webdriverio.js"
-    },
     "./test/plugins/browser-preview": {
+      "types": "./dist/test/plugins/browser-preview.d.ts",
       "default": "./dist/test/plugins/browser-preview.js"
     }
   },
   "dependencies": {
-    "@oxc-project/types": "=0.150.0",
+    "@oxc-project/types": "=0.151.0",
     "@oxlint/plugins": "=1.79.0",
-    "@vitest/browser": "4.1.11",
-    "@vitest/browser-preview": "4.1.11",
-    "@vitest/expect": "4.1.11",
-    "@vitest/mocker": "4.1.11",
-    "@vitest/pretty-format": "4.1.11",
-    "@vitest/runner": "4.1.11",
-    "@vitest/snapshot": "4.1.11",
-    "@vitest/spy": "4.1.11",
-    "@vitest/utils": "4.1.11",
-    "oxfmt": "=0.68.0",
-    "oxlint": "=1.83.0",
-    "oxlint-tsgolint": "=7.0.2001",
-    "vite": "npm:@voidzero-dev/vite-plus-core@0.3.3",
-    "vitest": "4.1.11"
+    "@vitest/browser": "5.0.1",
+    "@vitest/browser-preview": "5.0.1",
+    "@vitest/mocker": "5.0.1",
+    "@vitest/pretty-format": "5.0.1",
+    "@vitest/snapshot": "5.0.1",
+    "@vitest/spy": "5.0.1",
+    "@vitest/utils": "5.0.1",
+    "oxfmt": "=0.70.0",
+    "oxlint": "=1.85.0",
+    "oxlint-tsgolint": "=7.0.2003",
+    "vite": "npm:@voidzero-dev/vite-plus-core@1.0.0-rc.1",
+    "vitest": "5.0.1"
   },
   "devDependencies": {
     "@emnapi/core": "2.0.0-alpha.5",
@@ -384,9 +361,9 @@
     "@types/cross-spawn": "^6.0.6",
     "@types/semver": "^7.8.0",
     "@types/validate-npm-package-name": "^4.0.2",
-    "@vitest/browser-playwright": "4.1.11",
-    "@vitest/browser-webdriverio": "4.1.11",
-    "@voidzero-dev/vite-plus-prompts": "0.3.3",
+    "@vitest/browser-playwright": "5.0.1",
+    "@vitest/browser-webdriverio": "5.0.0",
+    "@voidzero-dev/vite-plus-prompts": "1.0.0-rc.1",
     "bingo": "^0.9.3",
     "cac": "^7.0.0",
     "cross-spawn": "^7.0.5",
@@ -394,7 +371,7 @@
     "detect-newline": "^4.0.1",
     "glob": "^13.0.0",
     "jsonc-parser": "^3.3.1",
-    "lint-staged": "^16.2.6",
+    "lint-staged": "^17.5.1",
     "minimatch": "^10.0.3",
     "nanotar": "^0.3.0",
     "picocolors": "^1.1.1",
@@ -405,8 +382,8 @@
     "zod": "^3.25.76"
   },
   "peerDependencies": {
-    "@vitest/browser-playwright": "4.1.11",
-    "@vitest/browser-webdriverio": "4.1.11"
+    "@vitest/browser-playwright": "5.0.1",
+    "@vitest/browser-webdriverio": "^5.0.0-beta.5 || >=5.0.0"
   },
   "peerDependenciesMeta": {
     "@vitest/browser-playwright": {
@@ -431,17 +408,17 @@
     ]
   },
   "engines": {
-    "node": "^20.19.0 || ^22.18.0 || >=24.11.0"
+    "node": "^22.18.0 || ^24.11.0 || >=26.0.0"
   },
   "optionalDependencies": {
-    "@voidzero-dev/vite-plus-darwin-arm64": "0.3.3",
-    "@voidzero-dev/vite-plus-darwin-x64": "0.3.3",
-    "@voidzero-dev/vite-plus-linux-arm64-gnu": "0.3.3",
-    "@voidzero-dev/vite-plus-linux-arm64-musl": "0.3.3",
-    "@voidzero-dev/vite-plus-linux-x64-gnu": "0.3.3",
-    "@voidzero-dev/vite-plus-linux-x64-musl": "0.3.3",
-    "@voidzero-dev/vite-plus-win32-x64-msvc": "0.3.3",
-    "@voidzero-dev/vite-plus-win32-arm64-msvc": "0.3.3"
+    "@voidzero-dev/vite-plus-darwin-arm64": "1.0.0-rc.1",
+    "@voidzero-dev/vite-plus-darwin-x64": "1.0.0-rc.1",
+    "@voidzero-dev/vite-plus-linux-arm64-gnu": "1.0.0-rc.1",
+    "@voidzero-dev/vite-plus-linux-arm64-musl": "1.0.0-rc.1",
+    "@voidzero-dev/vite-plus-linux-x64-gnu": "1.0.0-rc.1",
+    "@voidzero-dev/vite-plus-linux-x64-musl": "1.0.0-rc.1",
+    "@voidzero-dev/vite-plus-win32-x64-msvc": "1.0.0-rc.1",
+    "@voidzero-dev/vite-plus-win32-arm64-msvc": "1.0.0-rc.1"
   },
   "scripts": {
     "build": "oxnode -C dev ./build.ts",

package/bin/oxfmt

@@ -1,33 +0,0 @@
-#!/usr/bin/env node
-
-// LSP-only wrapper for oxfmt.
-// This enables IDE extensions (e.g., oxc-vscode) to discover and start the LSP server.
-// Binary resolution follows the same approach as `src/resolve-fmt.ts`.
-
-const isLSP = process.argv.includes('--lsp');
-const isStdin = process.argv.some((arg) => arg.startsWith('--stdin-filepath'));
-if (!isLSP && !isStdin) {
-  console.error('This oxfmt wrapper is for IDE extension use only (lsp or stdin mode).');
-  console.error('To format your code, run: vp fmt');
-  process.exit(1);
-}
-
-import { createRequire } from 'node:module';
-import { dirname, join } from 'node:path';
-import { pathToFileURL } from 'node:url';
-import pkg from '../package.json' with { type: 'json' };
-
-const require = createRequire(import.meta.url);
-const oxfmtMainPath = require.resolve('oxfmt');
-const oxfmtBin = join(dirname(dirname(oxfmtMainPath)), 'bin', 'oxfmt');
-
-// This allows oxfmt to load vite.config.ts.
-// For `vp check` and `vp fmt`, VP_VERSION is injected by
-// `merge_resolved_envs_with_version()` in `cli.rs`.
-process.env.VP_VERSION = pkg.version;
-// oxfmt reads vite.config.ts only for the `fmt` block, so skip the user's
-// Vite plugin factory (lazyPlugins) while the config evaluates.
-// Literal kept in sync with CONFIG_METADATA_ENV in src/utils/constants.ts
-// (this plain-JS bin can't import the bundled constant).
-process.env.VP_RESOLVING_CONFIG_METADATA ??= '1';
-await import(pathToFileURL(oxfmtBin).href);

package/bin/oxlint

@@ -1,38 +0,0 @@
-#!/usr/bin/env node
-
-// LSP-only wrapper for oxlint.
-// This enables IDE extensions (e.g., oxc-vscode) to discover and start the LSP server.
-// Binary resolution follows the same approach as `src/resolve-lint.ts`.
-
-if (!process.argv.includes('--lsp')) {
-  console.error('This oxlint wrapper is for IDE extension use only (--lsp mode).');
-  console.error('To lint your code, run: vp lint');
-  process.exit(1);
-}
-
-import { createRequire } from 'node:module';
-import { dirname, join } from 'node:path';
-import { pathToFileURL } from 'node:url';
-import { resolveTsgolintExecutable } from '../dist/tsgolint-path.js';
-import pkg from '../package.json' with { type: 'json' };
-
-const require = createRequire(import.meta.url);
-const oxlintMainPath = require.resolve('oxlint');
-const oxlintBin = join(dirname(dirname(oxlintMainPath)), 'bin', 'oxlint');
-const tsgolintPackageJsonPath = require.resolve('oxlint-tsgolint/package.json');
-const tsgolintBin = resolveTsgolintExecutable(
-  join(dirname(tsgolintPackageJsonPath), 'bin', 'tsgolint.js'),
-  import.meta.url,
-);
-
-// This allows oxlint to load vite.config.ts.
-// For `vp check` and `vp lint`, VP_VERSION is injected by
-// `merge_resolved_envs_with_version()` in `cli.rs`.
-process.env.VP_VERSION = pkg.version;
-// oxlint reads vite.config.ts only for the `lint` block, so skip the user's
-// Vite plugin factory (lazyPlugins) while the config evaluates.
-// Literal kept in sync with CONFIG_METADATA_ENV in src/utils/constants.ts
-// (this plain-JS bin can't import the bundled constant).
-process.env.VP_RESOLVING_CONFIG_METADATA ??= '1';
-process.env.OXLINT_TSGOLINT_PATH ??= tsgolintBin;
-await import(pathToFileURL(oxlintBin).href);