From 16952bf0f77fff9c8d09ddeafc9ba6bf2707fcf1 Mon Sep 17 00:00:00 2001 From: PJ Date: Sat, 22 Aug 2026 21:04:24 +0530 Subject: [PATCH] docs: say what a mismatched spec package and binary now do --- docs/manual/getting-started.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/manual/getting-started.md b/docs/manual/getting-started.md index 094ff94..e472b8b 100644 --- a/docs/manual/getting-started.md +++ b/docs/manual/getting-started.md @@ -20,7 +20,7 @@ The spec package, in your project: npm install --save-dev @sanderling/spec ``` -Both come from the same release tag, and the CLI bundles the package's TypeScript sources when it evaluates your spec, so upgrade them together. Pre-releases are published under npm's `next` tag; `npm install @sanderling/spec` gives you the current stable one. +Both come from the same release tag, and the CLI bundles the package's TypeScript sources when it evaluates your spec, so upgrade them together. A pair that disagrees about how an action is encoded fails the run at startup, naming both encodings, rather than dispatching every action successfully into the wrong gesture. Pre-releases are published under npm's `next` tag; `npm install @sanderling/spec` gives you the current stable one. ## Check your environment