@mpcore/vitest 1.0.0 → 1.1.0

package/README.md

@@ -40,3 +40,5 @@ test('renders a page', async ({ mpcore, expect }) => {
 ```
 
 `createMpcoreTest({ artifact: { projectPath: process.cwd() } })` still accepts an existing artifact directly. `createVitestProject()` also uses the configured artifact when omitted, and closes its runtime with the current test. Optional host mocks and `failOnConsoleError` can be passed without replacing the injected artifact. Calling either helper without a configured or explicit artifact reports an actionable error.
+
+Setup also registers the semantic tree snapshot serializer from `@mpcore/test`. Use `expect(result.screen).toMatchSnapshot()` or snapshot an individual node. Snapshots preserve public tree and event-binding semantics while removing runtime IDs, style scope markers and generated handler names. Full diagnostic snapshots returned by `page.snapshot()` remain unchanged; use `toMiniProgramSnapshot()` explicitly to serialize one.

package/dist/setup.mjs

@@ -1,6 +1,7 @@
-import { mpcoreMatchers } from "@mpcore/test";
+import { mpcoreMatchers, mpcoreSnapshotSerializer } from "@mpcore/test";
 import { expect } from "vitest";
 //#region src/setup.ts
 expect.extend(mpcoreMatchers);
+expect.addSnapshotSerializer(mpcoreSnapshotSerializer);
 //#endregion
 export {};

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@mpcore/vitest",
   "type": "module",
-  "version": "1.0.0",
+  "version": "1.1.0",
   "description": "Vitest integration for @mpcore/test",
   "author": "ice breaker <1324318532@qq.com>",
   "license": "MIT",
@@ -51,10 +51,10 @@
     "vitest": ">=5.0.0"
   },
   "dependencies": {
-    "@mpcore/test": "1.0.0"
+    "@mpcore/test": "1.1.0"
   },
   "devDependencies": {
-    "vitest": "~5.0.3"
+    "vitest": "~5.0.5"
   },
   "publishConfig": {
     "access": "public",