@forumone/throughline-design-contract 0.4.0 → 0.5.1

package/CHANGELOG.md

@@ -1,5 +1,84 @@
 # @forumone/throughline-design-contract
 
+## 0.5.1
+
+### Patch Changes
+
+- 957403b: One `@types/node`, so a host does not end up with two copies of `@payloadcms/ui`
+
+  Twelve packages asked for `@types/node@^20.17.0` and `design-system-payload`
+  asked for `^24.13.2`. Inside this repository that is untidy. Inside a host that
+  consumes the suite from source — which is how `forumone/forumone-2026` uses it,
+  as a git submodule in one pnpm workspace — it is a runtime failure.
+
+  pnpm hashes a package's identity with its resolved peers. `publishing` and
+  `integrations` both take `@payloadcms/ui` as a peer _and_ as a devDependency, so
+  each got its own copy resolved against `@types/node@20`, while the host's copy
+  resolved against `@types/node@24`. Same version, 3.87.1, two directories:
+
+      apps/web                     → @payloadcms+ui@3.87.1_…_9ce0de5c…
+      packages/publishing          → @payloadcms+ui@3.87.1_…_13184ec4…
+      packages/integrations        → @payloadcms+ui@3.87.1_…_13184ec4…
+
+  Two directories are two module instances. Two instances of `@payloadcms/ui` are
+  two `ConfigContext` objects, and `PublishButton` read the one the admin's
+  provider had never populated:
+
+      TypeError: Cannot destructure property 'config' of useConfig() as it is undefined
+
+  The host saw an intermittent 500 on every admin document view — `PublishButton`
+  is installed on each collection with a publish policy, so lists, `/admin` and
+  the login screen were all fine and only editing broke. Nothing caught it:
+  install, `--frozen-lockfile`, typecheck, lint and every test passed, because the
+  two copies are byte-identical and the split exists only at module resolution.
+  forumone/forumone-2026#498.
+
+  Aligning on `^24.13.2` collapses them to one instance. Nothing here targets a
+  Node 20 API deliberately; the packages typecheck and test unchanged against the
+  newer types.
+
+  `create-throughline` keeps `^20.17.0` on purpose. It is the one package
+  declaring `engines.node: >=20.9.0`, and typechecking a CLI against types newer
+  than the runtime it promises to support is how a Node 24-only call ships to
+  somebody on Node 20.
+
+## 0.5.0
+
+### Minor Changes
+
+- 45724ee: A contract can say a boolean starts ticked, and be believed
+
+  `boolean` fields were generated as `{ type: 'checkbox', defaultValue: false }`,
+  with the `false` hardcoded. That made a component's own default unreachable from
+  the CMS. A checkbox is stored ticked or unticked and never absent, so `coerce`
+  always had a value to turn into a real boolean, the prop was never `undefined`,
+  and a signature default like `hasFacade = true` could not apply. Every boolean a
+  contract described arrived at its component as `false`, whatever the component
+  said.
+
+  It was not theoretical. `VideoEmbed.hasFacade` exists to keep a provider's
+  iframe — several hundred kilobytes and its third-party cookies — off the page
+  until a reader presses play, and its contract says "Leave on". Every embed an
+  author added shipped with it off: the YouTube iframe was in the server HTML from
+  first paint, setting cookies on readers who never pressed play, on a site whose
+  stated rule is that no third-party tracking runs before consent.
+
+  So `ContentField` gains an optional `defaultValue`, read by the checkbox branch
+  and rejected on any other field type — anywhere else it is a value the author
+  expects to take effect and nothing ever would.
+
+  `allOrNothing` had to learn about it too. That rule treats `false` as "nobody
+  touched this", which is right for a checkbox that starts unticked and exactly
+  wrong for one that starts ticked: left alone, a group holding a ticked-by-default
+  boolean would never look empty, and the rule would demand the group's required
+  children of an author who had typed nothing. It now takes a field's declared
+  default into account rather than the value alone.
+
+  **Existing stored values are untouched.** `defaultValue` applies to a field an
+  author has not yet filled in, so blocks already saved keep whatever is in the
+  database; a `VideoEmbed` saved before this change still renders without its
+  facade until someone edits it.
+
 ## 0.4.0
 
 ### Minor Changes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@forumone/throughline-design-contract",
-  "version": "0.4.0",
+  "version": "0.5.1",
   "description": "The contract every AI-ready design system satisfies to be consumable by Throughline.",
   "type": "module",
   "main": "./dist/index.js",
@@ -43,12 +43,12 @@
     "zod": "^3.23.0"
   },
   "devDependencies": {
-    "@types/node": "^20.17.0",
+    "@types/node": "^24.13.2",
     "eslint": "^9.15.0",
     "typescript": "^5.6.0",
     "vitest": "^2.1.0",
-    "@forumone/throughline-tsconfig": "0.0.0",
-    "@forumone/throughline-eslint-config": "0.0.0"
+    "@forumone/throughline-eslint-config": "0.0.0",
+    "@forumone/throughline-tsconfig": "0.0.0"
   },
   "scripts": {
     "build": "tsc -b",