@uniweb/build 0.51.0 → 0.52.0

package/src/uwx/site.js

@@ -75,13 +75,14 @@ function setIf(obj, key, value) {
   if (value !== undefined) obj[key] = value
 }
 
-// A YAML scalar the author may have written unquoted: `20260910` loads as a number
-// and `2026-09-10` as a Date. Carry either as the string it stands for; anything
-// else that is not a string is not a value a string field can hold.
+// A YAML scalar the author may have written unquoted: `20260910` loads as a number.
+// Carry it as the string it stands for; anything else that is not a string is not a
+// value a string field can hold. (`2026-09-10` loads as the string it is written as —
+// the build's YAML resolves no timestamps, `utils/yaml-schema.js` — so no Date arrives:
+// it was carried re-rendered by `toISOString()` until 2026-09-14.)
 function scalarString(value) {
   if (typeof value === 'string') return value
   if (typeof value === 'number') return String(value)
-  if (value instanceof Date) return value.toISOString()
   return undefined
 }
 
@@ -289,7 +290,7 @@ function buildPageData(config, ctx) {
     // two data sources. The claim was here the whole time; the mirroring was not.
     // ⭐ `query`, END TO END — no crossing. An earlier version emitted `collection`
     // here on the belief that this field was the backend's to name. MEASURED
-    // otherwise: framework already ships `transform`, `detailPage`, `merge` and
+    // otherwise: framework was already shipping `transform`, `detailPage`, `merge` and
     // `prerender` inside this same `fetch` object, which no backend could be
     // validating — so `fetch` is a blob they carry and framework owns its
     // vocabulary. ⇒ There was nothing to coordinate, and inventing a coordination

package/src/validate-data.js

@@ -27,6 +27,7 @@ import { readFile } from 'node:fs/promises'
 import { existsSync } from 'node:fs'
 import { join, resolve, basename } from 'node:path'
 import yaml from 'js-yaml'
+import { YAML_OPTIONS } from './utils/yaml-schema.js'
 import { queryNameFromUrl, siteReaches, declaredKeys, fillDeclaredKeys } from '@uniweb/core'
 
 import { validateItem, isStaticallyCheckable, validateBound } from '@uniweb/schemas/conform'
@@ -541,13 +542,13 @@ async function resolveRecords(path, { byQuery, siteRoot }) {
     try {
       const text = await readFile(filePath, 'utf8')
       if (path.endsWith('.json')) records = JSON.parse(text)
-      else if (path.endsWith('.yml') || path.endsWith('.yaml')) records = yaml.load(text)
+      else if (path.endsWith('.yml') || path.endsWith('.yaml')) records = yaml.load(text, YAML_OPTIONS)
       else {
         // Unknown extension — try JSON, then YAML.
         try {
           records = JSON.parse(text)
         } catch {
-          records = yaml.load(text)
+          records = yaml.load(text, YAML_OPTIONS)
         }
       }
     } catch (err) {
@@ -555,12 +556,12 @@ async function resolveRecords(path, { byQuery, siteRoot }) {
     }
   }
 
-  // Validate the shape that actually SHIPS. `/data/*.json` is JSON, so a YAML
-  // date (parsed to a Date object in memory) serializes to an ISO string, while
-  // booleans / numbers / nesting are unchanged. Checking the JSON-round-tripped
-  // form makes the checker agree with the serialized payload the runtime and
-  // backend receive — and with the prerendered HTML oracle — so a string-typed
-  // date field isn't a false "expected string, got date".
+  // Validate the shape that actually SHIPS. `/data/*.json` is JSON, so anything a
+  // JSON round trip changes is checked as it arrives, while booleans / numbers /
+  // nesting are unchanged. Checking the JSON-round-tripped form makes the checker
+  // agree with the serialized payload the runtime and backend receive — and with the
+  // prerendered HTML oracle. (A YAML date no longer needs it: the build's YAML
+  // resolves no timestamps, `utils/yaml-schema.js`, so it is the string as written.)
   return { records: toShippedShape(records) }
 }