@uniweb/runtime 1.2.9 → 1.2.10

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@uniweb/runtime",
-  "version": "1.2.9",
+  "version": "1.2.10",
   "description": "Minimal runtime for loading Uniweb foundations",
   "type": "module",
   "exports": {
@@ -36,8 +36,8 @@
     "node": ">=22.12"
   },
   "dependencies": {
-    "@uniweb/core": "~1.4.11",
-    "@uniweb/theming": "~1.2.1"
+    "@uniweb/theming": "~1.2.1",
+    "@uniweb/core": "~1.4.11"
   },
   "devDependencies": {
     "@vitejs/plugin-react": "^4.5.2",

package/src/font-links.js

@@ -0,0 +1,23 @@
+import { FONT_LINKS_MARKER } from '@uniweb/theming'
+
+/**
+ * Give a page the theme's font links when it arrived without them.
+ *
+ * A built page carries them in its `<head>` (`@uniweb/build`), and so does a prerendered
+ * one (`injectPageContent` in `ssr-renderer.js`). A host that serves the shell alone and
+ * leaves every page to the browser carries neither. `ensureThemeCss` computes the links
+ * onto the graph for such a lane, but nothing put them on the page: the browser added the
+ * theme's CSS (`ThemeProvider`) and never its fonts, so every family the theme imports
+ * fell back to a system face. This is the browser's half of the prerender's font block,
+ * deduped on the same marker, so a page that already has them is left alone.
+ *
+ * @param {object} themeData - `website.themeData`, with the `links` block `@uniweb/theming` generated
+ * @param {Document|null} [doc]
+ * @returns {boolean} whether it added them
+ */
+export function injectFontLinks(themeData, doc = typeof document === 'undefined' ? null : document) {
+  const head = doc?.head
+  if (!head || !themeData?.links || head.innerHTML.includes(FONT_LINKS_MARKER)) return false
+  head.insertAdjacentHTML('beforeend', `${FONT_LINKS_MARKER}\n${themeData.links}`)
+  return true
+}

package/src/setup.js

@@ -31,6 +31,7 @@ import {
 import { ChildBlocks } from './components/PageRenderer.jsx'
 import Background from './components/Background.jsx'
 import { wireFoundationCapabilities, hydrateDataStore, ensureThemeCss } from './wire-foundation.js'
+import { injectFontLinks } from './font-links.js'
 import { navigateInApp } from './navigation.js'
 
 // Re-export so existing consumers importing hydrateDataStore from
@@ -274,6 +275,9 @@ export function initUniweb({ content, foundation, extensions = [], routingCompon
   if (typeof document === 'undefined' || !document.getElementById('uniweb-theme')) {
     ensureThemeCss(uniweb, foundation)
   }
+  // And the theme's font links, which the CSS alone does not bring: a page that came
+  // with neither would otherwise set every imported family in a system face.
+  injectFontLinks(uniweb.activeWebsite?.themeData)
 
   uniweb.routingComponents = routingComponents
   uniweb.localeSwitch = localeSwitch