@patterkit/runtime 0.14.1 → 0.14.3

package/CHANGELOG.md

@@ -33,6 +33,27 @@ version number always means the same runtime behaviour. This package is versione
 
 ## [Unreleased]
 
+## [0.14.3] - 2026-09-27
+
+### Fixed
+
+- **The JS zip's module builds work without npm.** The zip carried the npm package's module build,
+  which imports five other packages the zip never included, so copying it into a project and
+  importing it failed until you installed them from npm. The zip now carries builds of the runtime
+  and of `@patterkit/play-helpers` with their dependencies inside them, under
+  `@patterkit/runtime/dist/` and `@patterkit/play-helpers/dist/`. They carry their own registry as a
+  result; to share one registry between engines, install from npm. The npm package is unchanged.
+
+## [0.14.2] - 2026-09-27
+
+### Changed
+
+- **`@wildwinter/scoperegistry` is a peer dependency.** Your game and every engine in it share one
+  registry, so there must be exactly one copy in the install. As a peer, npm installs it once for all
+  of them, and if two packages ever need versions that can't be one copy, the install stops and says
+  so instead of quietly adding a second. npm installs it for you; with a package manager that doesn't
+  install peer dependencies, add `@wildwinter/scoperegistry` yourself.
+
 ## [0.14.1] - 2026-09-27
 
 ### Fixed

package/README.md

@@ -16,10 +16,14 @@ Three equivalent channels - pick whichever fits how you work; **no npm is requir
   [`play-js-v*` GitHub Release](https://github.com/patterkit/patter/releases) - this
   runtime as a plain download, symmetric with the Unity / Unreal / Godot plugin zips.
   It carries `patterplay.min.js` (the `<script>` drop-in: this runtime plus
-  `@patterkit/play-helpers` under one global), the module builds under `dist/` (ESM + CJS +
-  types, for vendoring into your own build), this README, the CHANGELOG, and two `demos/`
-  (the zero-build drop-in page and the interactive tour).
-- **npm**: `npm install @patterkit/runtime` (same version as the zip).
+  `@patterkit/play-helpers` under one global), the module builds of both packages under
+  `@patterkit/runtime/dist/` and `@patterkit/play-helpers/dist/` (ESM + CJS + types, with their
+  dependencies inside them, so they need nothing installed), this README, the CHANGELOG, and two
+  `demos/` (the zero-build drop-in page and the interactive tour). The zip's builds carry their own
+  registry; to share one registry between engines, install from npm.
+- **npm**: `npm install @patterkit/runtime` (same version as the zip). `@wildwinter/scoperegistry`
+  is a peer dependency, so a game holds one registry that every engine shares; npm installs it for
+  you, and a package manager that doesn't install peers needs `npm install @wildwinter/scoperegistry`.
 - **CDN**: `patterplay.min.js` via unpkg/jsDelivr from `@patterkit/play-helpers` (the package
   that builds it), or loose on the same Release.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@patterkit/runtime",
-  "version": "0.14.1",
+  "version": "0.14.3",
   "description": "Patter reference runtime: load a bundle and play dialogue - flows, selectors, choices, jumps, effects, properties. Built on @wildwinter/expr + scoperegistry.",
   "type": "module",
   "license": "MIT",
@@ -38,7 +38,12 @@
     "@patterkit/model": ">=0.4.0 <1.0.0",
     "@patterkit/dialect": ">=0.1.6 <1.0.0",
     "@wildwinter/expr": "^0.5.0",
-    "@wildwinter/expr-specificity": "^0.1.0",
+    "@wildwinter/expr-specificity": "^0.1.0"
+  },
+  "peerDependencies": {
+    "@wildwinter/scoperegistry": ">=0.7.0 <1.0.0"
+  },
+  "devDependencies": {
     "@wildwinter/scoperegistry": ">=0.7.0 <1.0.0"
   }
 }