@uniweb/core 0.26.0 → 0.26.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@uniweb/core",
-  "version": "0.26.0",
+  "version": "0.26.2",
   "description": "Core classes for the Uniweb platform - Uniweb, Website, Page, Block",
   "type": "module",
   "exports": {
@@ -44,8 +44,8 @@
     "vitest": "^4.1.7"
   },
   "dependencies": {
-    "@uniweb/theming": "^0.1.15",
-    "@uniweb/semantic-parser": "^1.4.0"
+    "@uniweb/semantic-parser": "^1.4.0",
+    "@uniweb/theming": "^0.1.15"
   },
   "scripts": {
     "test": "vitest run"

package/src/index.js

@@ -71,6 +71,7 @@ export {
   routeParamName,
   parentRouteOf,
   recordRouteBase,
+  findPageForRoute,
 } from './route-match.js'
 export { isRichSchema } from './schemas.js'
 // ⛔ `Tracker` is NOT on the package entry. It is a FEATURE, not part of the

package/src/page.js

@@ -600,11 +600,23 @@ export default class Page {
    * is "give me the page to render *here*," not "give me the next URL
    * with content."
    *
-   * Used by SSR paths (Cloudflare Worker isolate today; framework SSG
-   * pre-handles this differently via expandDynamicPages) to avoid
-   * rendering nothing when an author requests `/docs` and the page is
-   * a folder whose actual landing content lives in `/docs/intro` flagged
-   * as `isIndex: true`.
+   * The case it exists for: an author requests `/docs`, the page is a folder
+   * with no content of its own, and its actual landing content lives in
+   * `/docs/intro` flagged `isIndex: true`.
+   *
+   * ⭐ **ONE CALLER, AND IT IS THE RULE FOR BOTH OF THE RENDERER'S TARGET FORMS:**
+   * `createPageRenderer().render()` (`@uniweb/runtime`) applies this after
+   * resolving, so a route and an already-resolved Page promote identically.
+   * Ruled 2026-09-12 [Diego], closing an asymmetry in which the same page rendered
+   * differently depending on which form the caller held — silently, with no error
+   * on either path.
+   *
+   * ⚠️ **It briefly had NO caller** (2026-09-12), after an SSR consumer replaced its
+   * hand-composed sequence with `render()`. An earlier version of this paragraph
+   * named that consumer and claimed the static build "pre-handles this differently
+   * via expandDynamicPages"; **both halves were wrong** — the static build never
+   * called this at all: it emits a redirect to the first descendant with content
+   * (`getNavigableRoute`) rather than promoting anything.
    *
    * @returns {Page} The page to render — `this` or its index child.
    */

package/src/route-match.js

@@ -556,3 +556,49 @@ export function stripLocalePrefix(route, activeLocale, defaultLocale) {
   if (route.startsWith(`${prefix}/`)) return route.slice(prefix.length)
   return route
 }
+
+/**
+ * ⭐ **THE PAGE A ROUTE NAMES — one rule, for every lane that asks the question.**
+ *
+ * Exact match first, then the parametric pages in page order, which is the order
+ * `Website#getPage` uses in the SPA. Captured params are decoded by
+ * `matchDynamicRoute` (a catch-all per segment), so the values are what a site's
+ * query binds against.
+ *
+ * ⛔ **Why this is a leaf rather than a thing each lane composes.** More than one
+ * lane asks *which page does this path name* — the SPA, the runtime's server-side
+ * prefetch, and a host's router. Our leaves (`normalizeRoute`, `isDynamicRoute`,
+ * `routePatternToRegex`) were importable and the RULE was not, so a consumer
+ * imported the parts and wrote the composition itself. **A renamed export breaks
+ * loudly; a re-implemented rule drifts silently.** A hand-written matcher spelled
+ * `:(\w+)` accepts a different param alphabet than our `[A-Za-z0-9_-]+`, so a
+ * hyphenated slug resolves in one copy and 404s in the other, with nothing failing
+ * anywhere. Import this; do not rebuild it.
+ *
+ * ⚠️ **A trailing slash is the same route, on BOTH branches** (`normalizeRoute`),
+ * which is what `Website#getPage` has always done. The runtime's own prefetch copy
+ * compared raw strings until 2026-09-12 and so disagreed with the SPA about
+ * `/about/` — the exact class of split this function exists to end.
+ *
+ * ⚖️ Matching is not resolving: a hit means the ROUTE exists. Whether the record
+ * behind a parametric page exists is a data question answered later.
+ *
+ * @param {Array<Object>|{pages?: Array<Object>}} source - the pages, or a payload holding them
+ * @param {string} route - the concrete path
+ * @returns {{ page: Object|null, params: Record<string,string> }} `page` is null when nothing matches
+ */
+export function findPageForRoute(source, route) {
+  const pages = Array.isArray(source) ? source : source?.pages
+  const list = Array.isArray(pages) ? pages : []
+  const wanted = normalizeRoute(route)
+
+  for (const page of list) {
+    if (typeof page?.route === 'string' && normalizeRoute(page.route) === wanted) return { page, params: {} }
+  }
+  for (const page of list) {
+    if (typeof page?.route !== 'string' || !isDynamicRoute(page.route)) continue
+    const hit = matchDynamicRoute(page.route, wanted)
+    if (hit) return { page, params: hit.params }
+  }
+  return { page: null, params: {} }
+}