create-eigen-game 0.9.2 → 0.9.3

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-eigen-game",
-  "version": "0.9.2",
+  "version": "0.9.3",
   "license": "MIT",
   "description": "Scaffold an EigenInteractive game Worker and Flutter app without cloning the engine repositories.",
   "type": "module",
@@ -29,9 +29,9 @@
     "vitest": "^4.1.10",
     "wrangler": "^4.110.0",
     "zod": "^4.4.3",
-    "@eigeninteractive/rules": "0.2.5",
-    "@eigeninteractive/server": "0.2.5",
-    "@eigeninteractive/testkit": "0.2.5"
+    "@eigeninteractive/rules": "0.3.0",
+    "@eigeninteractive/server": "0.3.0",
+    "@eigeninteractive/testkit": "0.3.0"
   },
   "engines": {
     "node": ">=22"

package/templates/worker/package.json

@@ -31,6 +31,7 @@
     "contract:check": "eigen-contract --check",
     "deploy": "wrangler d1 migrations apply GAME_DB --remote && wrangler deploy",
     "dev": "{{PACKAGE_MANAGER}} run db:migrate:local && wrangler dev",
+    "inspect": "eigen-inspect",
     "start": "{{PACKAGE_MANAGER}} run db:migrate:local && wrangler dev",
     "test": "vitest run",
     "test:watch": "vitest",

package/templates/worker/tsconfig.json

@@ -11,5 +11,5 @@
     "skipLibCheck": true,
     "types": ["./worker-configuration.d.ts", "node"]
   },
-  "include": ["src", "test", "worker-configuration.d.ts"]
+  "include": ["src", "test", "worker-configuration.d.ts", "vitest.config.mts"]
 }

package/templates/worker/vitest.config.mts

@@ -0,0 +1,24 @@
+import { configDefaults, defineConfig } from "vitest/config";
+
+/**
+ * The twin fixtures are read with `readFileSync` at collect time, so they are
+ * not in Vite's module graph, and `test:watch` would ignore a fixture-only
+ * edit: Vitest looks a changed path up in the graph, finds nothing, and reruns
+ * nothing. `forceRerunTriggers` is the supported way to watch a file consumed
+ * outside the graph, and Vitest's own defaults use it for `package.json` and
+ * the config files for exactly that reason.
+ *
+ * Spread the defaults rather than replacing them. Config resolution is a
+ * shallow merge, so a bare array silently stops manifest and config edits from
+ * triggering a rerun.
+ *
+ * A match reruns the whole suite rather than one file. That is cheap here
+ * because these tests are pure Node. Keep the trigger off any
+ * `@cloudflare/vitest-pool-workers` project added later, where a fixture
+ * cannot change the result and the rebuild is not free.
+ */
+export default defineConfig({
+  test: {
+    forceRerunTriggers: [...configDefaults.forceRerunTriggers, "**/src/module/fixtures/**/*.json"],
+  },
+});