@uniweb/build 0.15.10 → 0.15.12

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@uniweb/build",
-  "version": "0.15.10",
+  "version": "0.15.12",
   "description": "Build tooling for the Uniweb Component Web Platform",
   "type": "module",
   "exports": {
@@ -57,15 +57,15 @@
     "@citestyle/bibtex": "^1.1.0",
     "esbuild": "^0.21.0 || ^0.23.0 || ^0.24.0 || ^0.25.0 || ^0.27.0",
     "js-yaml": "^4.1.0",
-    "sharp": "^0.33.2",
+    "sharp": "^0.35.3",
     "yaml": "^2.5.0",
-    "@uniweb/projections": "0.1.4",
-    "@uniweb/content-writer": "0.2.9",
-    "@uniweb/theming": "0.1.14"
+    "@uniweb/theming": "0.1.14",
+    "@uniweb/projections": "0.1.5",
+    "@uniweb/content-writer": "0.2.9"
   },
   "optionalDependencies": {
     "@uniweb/content-reader": "1.1.17",
-    "@uniweb/runtime": "0.8.39",
+    "@uniweb/runtime": "0.8.41",
     "@uniweb/schemas": "0.2.4"
   },
   "peerDependencies": {
@@ -75,7 +75,7 @@
     "@tailwindcss/vite": "^4.0.0",
     "@vitejs/plugin-react": "^4.0.0 || ^5.0.0",
     "vite-plugin-svgr": "^4.0.0",
-    "@uniweb/core": "0.7.32"
+    "@uniweb/core": "0.7.33"
   },
   "peerDependenciesMeta": {
     "vite": {

package/src/generate-entry.js

@@ -186,6 +186,15 @@ function generateEntrySource(components, options = {}) {
     const capParts = []
     if (foundationExports) {
       capParts.push('..._foundationModule.default')
+      // `vars` is a NAMED export of main.js, so the spread above misses it —
+      // schema.js reads `module.vars || module.default?.vars` and this must
+      // agree with it (named wins), or the runtime and the editor would see
+      // different foundation vars. Without this line the declared theme vars
+      // exist ONLY in dist/meta/schema.json, which is a build-time artifact:
+      // any lane that generates theme CSS outside the build (the runtime's
+      // ensureThemeCss, a cloud shell assembler) would silently produce a
+      // theme missing every foundation-declared var.
+      capParts.push('vars: _foundationModule.vars || _foundationModule.default?.vars')
     }
     if (layoutNames.length > 0) {
       capParts.push(`layouts: { ${layoutNames.join(', ')} }`)

package/src/prerender.js

@@ -383,6 +383,19 @@ export function injectBuildData(html, siteContent, { splitContent = false, curre
 
   // Inject the theme's font <link> tags if not already present (the vite
   // plugin normally puts them there when it builds index.html)
+  //
+  // STILL HERE, and it is the remaining half of the 2026-07-28 seam fix.
+  // `theme.links` is graph-derived like the theme CSS was, so by the rule
+  // below it belongs in injectPageContent() too — a lane that doesn't run
+  // this build gets no webfont <link>s and falls back to system fonts.
+  // What blocks the move is the marker, not the principle: FONT_LINKS_MARKER
+  // has a second consumer in site/plugin.js (the vite plugin), which must not
+  // import the SSR bundle, and @uniweb/build declares no dependency on
+  // @uniweb/runtime — so there is no one place both sides can read it from
+  // today. Fixing that means giving the runtime a zero-dep leaf export for
+  // the constant and re-exporting it here. Degraded-not-broken (wrong
+  // typeface, not unstyled), which is why it was scoped out rather than
+  // rushed.
   if (siteContent?.theme?.links && !result.includes(FONT_LINKS_MARKER)) {
     result = result.replace(
       '</head>',
@@ -390,13 +403,13 @@ export function injectBuildData(html, siteContent, { splitContent = false, curre
     )
   }
 
-  // Inject theme CSS if not already present
-  if (siteContent?.theme?.css && !result.includes('id="uniweb-theme"')) {
-    result = result.replace(
-      '</head>',
-      `  <style id="uniweb-theme">\n${siteContent.theme.css}\n    </style>\n  </head>`
-    )
-  }
+  // Theme CSS is NOT injected here. Like the appearance boot script below, it
+  // is derived from the website graph (`website.themeData`), so it belongs to
+  // the shared seam — @uniweb/runtime/ssr's injectPageContent(), which runs
+  // just before this — and every lane gets it from one implementation. It sat
+  // here until 2026-07-28 and cloud-rendered pages were unstyled the whole
+  // time. See the "which side of the seam?" note there before adding a new
+  // head injection, and note that this file has now got it wrong twice.
 
   // The pre-paint appearance script is NOT injected here. It belongs to the
   // shared seam — @uniweb/runtime/ssr's injectPageContent(), which runs just