@shivaedev/test-story 0.17.0 → 0.18.1

package/CHANGELOG.md

@@ -1,5 +1,17 @@
 # Changelog
 
+## 0.18.1 - 2026-10-24
+
+### Changed
+
+- Align published dependency and peer pins and the generated starter with React and React DOM 19.3.1, TanStack Router 1.170.45, Better Auth 1.7.10, happy-dom 21.0.3 and Vitest 5.0.5. The starter also uses pg-boss dashboard 1.12.1.
+
+## 0.18.0 - 2026-10-21
+
+### Breaking
+
+- Test-story's peers are exactly Vitest 5.0.4 and happy-dom 21.0.1. Consumers pin `vitest` to 5.0.4 and, when they run DOM stories, `happy-dom` to 21.0.1; happy-dom remains optional for applications without DOM stories.
+
 ## 0.17.0 - 2026-10-19
 
 ### Added

package/README.md

@@ -480,7 +480,7 @@ The package wraps between words or JSON fields toward 120 columns and prints the
 
 ### Library package kits
 
-A library package has an engine too: its own services or Layer under test. Keep its kit in `src/test-support/`, acquire the real services in `create` or a trait inside the story's per-test Scope, with their dependencies supplied by the kit's `layer`, and use real PostgreSQL wherever the package touches it. Traits seed that engine in domain words; each verb calls one action on the package's public API or reads one observation from that same engine. Verbs never create a fresh service just to run a scenario and return its measurements. The same division applies as for an application: the kit owns setup and wiring, and a spec names traits, shows every action through verbs and states each expectation. Following the [root test guidance](https://github.com/ShivaeDev/platform/blob/main/AGENTS.md), reserve plain Vitest tests for pure functions with no engine behind them.
+A library package has an engine too: its own services or Layer under test. Keep its kit in `src/test-support/`, acquire the real services in `create` or a trait inside the story's per-test Scope, with their dependencies supplied by the kit's `layer`, and use real PostgreSQL wherever the package touches it. Traits seed that engine in domain words; each verb calls one action on the package's public API or reads one observation from that same engine. Verbs never create a fresh service just to run a scenario and return its measurements. The same division applies as for an application: the kit owns setup and wiring, and a spec names traits, shows every action through verbs and states each expectation. Following the [root test guidance](https://github.com/ShivaeDev/platform/blob/main/AGENTS.md), a pure function with no engine behind it gets a plain Vitest test in a `.unit` file, such as `parse.unit.test.ts`, which Quality checks reaches no engine and mocks nothing. Never wrap a pure function in a story that ignores its kit.
 
 The [`backfill` kit](https://github.com/ShivaeDev/platform/blob/main/packages/effect-test-sql/src/test-support/migrationStory.ts) in `effect-test-sql` is a library example. Its `create` returns the package's `migrationSteps(migrations)` API, its worker Layer provides PostgreSQL, and `around: withIsolatedDatabase` isolates each story. The `oldSchema` and `existingContacts` traits put contacts with email addresses into the old schema; the `backfill` verb calls `steps.migrateToLatest`. Its [story](https://github.com/ShivaeDev/platform/blob/main/packages/effect-test-sql/src/server/migrationStory.spec.ts) proves that those existing addresses survive the migration into a new table. It runs only when `PLATFORM_EFFECT_TEST_SQL_TEST_DATABASE_URL` is configured; a skipped story proves nothing.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@shivaedev/test-story",
-  "version": "0.17.0",
+  "version": "0.18.1",
   "description": "Tests that read like stories over the real engine: a story kit per engine with its own it, traits per feature, and a failure that prints the story, where it stopped and the engine's state",
   "homepage": "https://github.com/ShivaeDev/platform/tree/main/packages/test-story#readme",
   "bugs": {
@@ -46,18 +46,18 @@
   },
   "devDependencies": {
     "@effect/vitest": "4.0.4",
-    "@shivaedev/quality": "0.30.0",
+    "@shivaedev/quality": "0.33.2",
     "@types/node": "24.19.2",
     "effect": "4.0.4",
-    "happy-dom": "20.14.6",
+    "happy-dom": "21.0.3",
     "typescript": "7.0.2",
-    "vitest": "5.0.3"
+    "vitest": "5.0.5"
   },
   "peerDependencies": {
     "@effect/vitest": "4.0.4",
     "effect": "4.0.4",
-    "happy-dom": "20.14.6",
-    "vitest": "5.0.3"
+    "happy-dom": "21.0.3",
+    "vitest": "5.0.5"
   },
   "peerDependenciesMeta": {
     "happy-dom": {