@uiverify/vitest 0.1.0 → 1.0.0

package/README.md

@@ -44,7 +44,7 @@ import { render } from "vitest-browser-react"; // or your framework's browser re
 import { takeSnapshot, disableAutoSnapshot } from "@uiverify/vitest";
 
 test("menu", async () => {
-  render(<Menu />);
+  await render(<Menu />); // render() is async - await it so the DOM is committed before capture
   await takeSnapshot("closed"); // optional named checkpoint
   // the final state is archived automatically at the end of the test
 });

package/dist/plugin.js

@@ -32,6 +32,12 @@ var SETUP_MODULE = "@uiverify/vitest/browser-setup";
 function uiverifyPlugin(options = {}) {
   const outDir = options.outDir ?? resolveOutDir();
   const config = {
+    // The capture state (`currentTask`) lives in module scope in `runtime.ts`, shared between the setup
+    // file's hooks and the user's `takeSnapshot` import. Dep pre-bundling would give those two entry
+    // points separate copies of that module, so `takeSnapshot()` would not see the running test and throw
+    // "called outside a test". Excluding the package from optimize keeps everyone on one instance, so a
+    // plain `plugins: [uiverifyPlugin()]` works without the user hand-adding this to their config.
+    optimizeDeps: { exclude: ["@uiverify/vitest"] },
     test: {
       setupFiles: [SETUP_MODULE],
       provide: { __uiverify: { disableAutoSnapshot: options.disableAutoSnapshot ?? false } },

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@uiverify/vitest",
-  "version": "0.1.0",
+  "version": "1.0.0",
   "description": "Vitest browser-mode capture SDK for UI Verify (uiverify.ai): add uiverifyPlugin() to your Vitest config and each browser-mode test archives its final DOM (serialized DOM + resource bytes) to be replayed + visually diffed by UI Verify. Produces an archive the uiverify CLI uploads; talks to nothing at runtime.",
   "keywords": [
     "visual-testing",