@uniweb/build 0.36.0 → 0.37.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@uniweb/build",
3
- "version": "0.36.0",
3
+ "version": "0.37.0",
4
4
  "description": "Build tooling for the Uniweb Component Web Platform",
5
5
  "type": "module",
6
6
  "exports": {
@@ -59,15 +59,15 @@
59
59
  "js-yaml": "^4.1.0",
60
60
  "sharp": "^0.35.3",
61
61
  "yaml": "^2.5.0",
62
- "@uniweb/semantic-parser": "^1.4.0",
63
62
  "@uniweb/content-writer": "^0.3.4",
64
- "@uniweb/theming": "^0.1.15",
65
63
  "@uniweb/content-reader": "^1.2.4",
64
+ "@uniweb/projections": "^0.5.7",
66
65
  "@uniweb/schemas": "^0.2.13",
67
- "@uniweb/projections": "^0.5.7"
66
+ "@uniweb/theming": "^0.1.15",
67
+ "@uniweb/semantic-parser": "^1.4.0"
68
68
  },
69
69
  "optionalDependencies": {
70
- "@uniweb/runtime": "^0.14.0"
70
+ "@uniweb/runtime": "^0.14.1"
71
71
  },
72
72
  "peerDependencies": {
73
73
  "vite": "^5.0.0 || ^6.0.0 || ^7.0.0",
@@ -429,12 +429,10 @@ export function parseFetchConfig(fetch) {
429
429
  // ⭐ **`as` is the BINDING KEY** — the `content.data.<key>` a component
430
430
  // reads — defaulting to the query name. It was called `schema` until
431
431
  // 2026-09-02, which collided with the MODEL REF of the same name on a
432
- // `queries` declaration. `fetch.schema` is still accepted as INPUT, so
433
- // content authored before the rename keeps working; it is never emitted.
434
- // `fetch.schema` here is an AUTHOR's older spelling in a content file —
435
- // the same boundary normalization as the source-shape branch below, not
436
- // the internal alias (removed 2026-09-02). One name travels inside.
437
- as: fetch.as || fetch.schema || fetch.query,
432
+ // `queries` declaration. **The old spelling is NOT read here, by
433
+ // ruling (2026-09-03): one name, no alias.** A fetch authored as
434
+ // `schema: posts` binds to nothing and is re-authored, not translated.
435
+ as: fetch.as || fetch.query,
438
436
  prerender: fetch.prerender ?? true,
439
437
  merge: fetch.merge ?? false,
440
438
  transform: fetch.transform,
@@ -455,7 +453,6 @@ export function parseFetchConfig(fetch) {
455
453
  path,
456
454
  url,
457
455
  as,
458
- schema,
459
456
  prerender = url ? false : true,
460
457
  merge = false,
461
458
  transform,
@@ -477,12 +474,10 @@ export function parseFetchConfig(fetch) {
477
474
  return {
478
475
  path,
479
476
  url,
480
- // **The one place `schema` is still read, and it is a BOUNDARY
481
- // normalization not the internal alias.** An author may have written
482
- // `fetch: { schema: person }` before the 2026-09-02 rename; that is content
483
- // on someone's disk, not a field our own packages pass to each other.
484
- // Translating it here means one name — `as` — everywhere inside.
485
- as: as ?? schema ?? inferSchemaFromPath(path || url),
477
+ // `schema` is NOT read here by ruling (2026-09-03), the retired
478
+ // spelling has no alias anywhere, authored content included. A fetch that
479
+ // still says `schema:` gets the inferred key and is re-authored to `as:`.
480
+ as: as ?? inferSchemaFromPath(path || url),
486
481
  prerender,
487
482
  merge,
488
483
  transform,