@uniweb/build 0.33.0 → 0.34.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@uniweb/build",
-  "version": "0.33.0",
+  "version": "0.34.0",
   "description": "Build tooling for the Uniweb Component Web Platform",
   "type": "module",
   "exports": {
@@ -60,14 +60,14 @@
     "sharp": "^0.35.3",
     "yaml": "^2.5.0",
     "@uniweb/schemas": "^0.2.13",
-    "@uniweb/projections": "^0.5.4",
-    "@uniweb/theming": "^0.1.15",
     "@uniweb/content-reader": "^1.2.4",
+    "@uniweb/theming": "^0.1.15",
     "@uniweb/semantic-parser": "^1.4.0",
+    "@uniweb/projections": "^0.5.5",
     "@uniweb/content-writer": "^0.3.4"
   },
   "optionalDependencies": {
-    "@uniweb/runtime": "^0.13.5"
+    "@uniweb/runtime": "^0.13.6"
   },
   "peerDependencies": {
     "vite": "^5.0.0 || ^6.0.0 || ^7.0.0",
@@ -76,7 +76,7 @@
     "@tailwindcss/vite": "^4.0.0",
     "@vitejs/plugin-react": "^4.0.0 || ^5.0.0",
     "vite-plugin-svgr": "^4.0.0",
-    "@uniweb/core": "^0.16.0"
+    "@uniweb/core": "^0.17.0"
   },
   "peerDependenciesMeta": {
     "vite": {

package/src/site/data-fetcher.js

@@ -349,8 +349,28 @@ export function parseFetchConfig(fetch) {
     warnUnknownFetchKeys(fetch, 'query')
     if (fetch.filter !== undefined) warnFilterDeprecated()
     return {
+      // ⭐ **`query` IS EMITTED, and that is what makes the two producers agree.**
+      // The sync lane has always emitted it (`uwx/site.js`) and this one did not,
+      // for the same declaration — so `resolveQuerySource` fired on a published
+      // site and never on a `--link`-deployed one. Measured 2026-09-02 against a
+      // host declaring `config.records`:
+      //
+      //   --link   endpoint undefined, path /data/articles.json   ← the STATIC file
+      //   publish  endpoint /_api/q/articles                       ← the live lane
+      //
+      // Same site, same declaration, two verbs, two data sources. Publishing to a
+      // platform that declares a live lane is supposed to READ from it — the
+      // compiled `/data/*.json` is the escape hatch for entities with no known
+      // data schema, which never sync, not a second way to serve the ones that do.
+      //
+      // ⚠️ Not in the cache key: `deriveCacheKey` hashes {path,url,endpoint,schema,
+      // transform}, so adding this moves no cached entry.
+      query: fetch.query,
       path: queryDataUrl(fetch.query),
       url: undefined,
+      // The BINDING KEY — the `content.data.<key>` a component reads. Defaults to
+      // the query name, which is why the two were confusable; `query` above now
+      // carries the identity so this one only has to carry the key.
       schema: fetch.schema || fetch.query,
       prerender: fetch.prerender ?? true,
       merge: fetch.merge ?? false,

package/src/uwx/site.js

@@ -251,7 +251,11 @@ function buildPageData(config, ctx) {
     //
     // `schema` (the query name) is BOTH the content.data key and part of the
     // dataStore cache key (deriveCacheKey hashes {path,url,endpoint,schema,…};
-    // the shorthand is ignored). Mirrors the static build's parseFetchConfig.
+    // the shorthand is ignored). Mirrors the static build's parseFetchConfig —
+    // ⚠️ which it did NOT until 2026-09-02. This line emitted `query` and that
+    // one did not, for the same declaration, so `resolveQuerySource` fired on a
+    // published site and never on a `--link`-deployed one: same site, two verbs,
+    // 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