@uniweb/build 0.16.4 → 0.16.6

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@uniweb/build",
-  "version": "0.16.4",
+  "version": "0.16.6",
   "description": "Build tooling for the Uniweb Component Web Platform",
   "type": "module",
   "exports": {
@@ -59,15 +59,15 @@
     "js-yaml": "^4.1.0",
     "sharp": "^0.35.3",
     "yaml": "^2.5.0",
-    "@uniweb/theming": "0.1.15",
     "@uniweb/content-writer": "0.3.3",
-    "@uniweb/projections": "0.2.3"
+    "@uniweb/projections": "0.2.3",
+    "@uniweb/theming": "0.1.15"
   },
   "optionalDependencies": {
     "@uniweb/content-reader": "1.2.2",
-    "@uniweb/semantic-parser": "1.2.0",
-    "@uniweb/runtime": "0.9.0",
-    "@uniweb/schemas": "0.2.4"
+    "@uniweb/runtime": "0.9.1",
+    "@uniweb/schemas": "0.2.4",
+    "@uniweb/semantic-parser": "1.2.0"
   },
   "peerDependencies": {
     "vite": "^5.0.0 || ^6.0.0 || ^7.0.0",

package/src/runtime-schema.js

@@ -359,6 +359,7 @@ export function extractAllRuntimeSchemas(componentsMeta, dataSchemaMap = {}) {
  *   this overrides per region, or `false` opts the layout out)
  * - defaults: Param default values
  * - scroll: Scroll management mode ('self' or CSS selector)
+ * - layers: Stacking order of the area wrappers (object, or false to opt out)
  *
  * @param {Object} fullMeta - The full meta.js default export for a layout
  * @returns {Object|null} - Lean layout runtime schema or null if empty
@@ -374,10 +375,21 @@ export function extractLayoutRuntimeSchema(fullMeta) {
     runtime.areas = fullMeta.areas
   }
 
-  if (fullMeta.transitions && typeof fullMeta.transitions === 'object') {
+  // `false` is a value, not an absence: it is the documented way a layout opts
+  // out of per-area view transitions. The previous guard was
+  // `fullMeta.transitions && typeof … === 'object'`, which is false for `false`
+  // — so the opt-out was dropped here and never reached the runtime, even
+  // though `resolveLayoutTransitions` has always handled it. Same for `layers`.
+  if (fullMeta.transitions === false || (fullMeta.transitions && typeof fullMeta.transitions === 'object')) {
     runtime.transitions = fullMeta.transitions
   }
 
+  // Stacking order of the area wrappers. Carried whether or not the layout
+  // declares transitions, because an explicit layer is itself a reason to wrap.
+  if (fullMeta.layers === false || (fullMeta.layers && typeof fullMeta.layers === 'object')) {
+    runtime.layers = fullMeta.layers
+  }
+
   if (fullMeta.scroll !== undefined) {
     runtime.scroll = fullMeta.scroll
   }

package/src/schema.js

@@ -120,6 +120,63 @@ export async function loadPackageJson(srcDir) {
  * - props: Foundation-wide props
  * - Future: providers, middleware, etc.
  */
+/**
+ * Capability keys that only work as keys of the DEFAULT export.
+ *
+ * The list is `cli/partials/agents.md`'s ("A single `export default { … }` whose
+ * top-level keys are the capabilities the foundation provides"). `vars` is
+ * deliberately absent: it is the one capability that also works named, because
+ * `generate-entry.js` reads it explicitly.
+ */
+const DEFAULT_ONLY_CAPABILITIES = [
+  'name',
+  'description',
+  'defaultLayout',
+  'defaultSection',
+  'viewTransitions',
+  'props',
+  'defaultInsets',
+  'xref',
+  'outputs',
+  'handlers',
+  'extension',
+]
+
+/**
+ * Warn when a capability was written as a named export.
+ *
+ * `generate-entry.js` builds `capabilities` as `{ ..._foundationModule.default,
+ * vars: … }` — it spreads only the DEFAULT export. A named `export const xref =
+ * …` is therefore dropped with no error, no warning, and a build that succeeds.
+ * Whatever the capability did simply does not happen, which reads as "the
+ * feature is not implemented" rather than "it is declared in the wrong place".
+ *
+ * Real incident (2026-07-31): cross-references were wired onto uniweb.io as
+ * named `xref` and `defaultInsets` exports. The build passed, the site ran, and
+ * every `[#id]` rendered as its own literal text — indistinguishable from a
+ * foundation that had never opted in. Found only by reading generate-entry.js.
+ *
+ * A warning rather than an error: a foundation may legitimately export a name
+ * that collides for its own use, and failing someone's build over a naming
+ * coincidence is worse than telling them what we ignored.
+ */
+function warnMisplacedCapabilities(module, filePath) {
+  const onDefault = module.default && typeof module.default === 'object' ? module.default : {}
+  const misplaced = DEFAULT_ONLY_CAPABILITIES.filter(
+    key => module[key] !== undefined && onDefault[key] === undefined,
+  )
+  if (misplaced.length === 0) return
+
+  const list = misplaced.map(k => `\`${k}\``).join(', ')
+  console.warn(
+    `Warning: ${filePath} exports ${list} as named export${misplaced.length > 1 ? 's' : ''}, ` +
+      `which the build ignores.\n` +
+      `  Capabilities are read from the default export only — move ${misplaced.length > 1 ? 'them' : 'it'} into ` +
+      `\`export default { … }\`.\n` +
+      `  (\`vars\` is the exception and may stay a named export.)`,
+  )
+}
+
 export async function loadFoundationConfig(srcDir) {
   let filePath = null
   for (const name of FOUNDATION_FILE_NAMES) {
@@ -133,6 +190,7 @@ export async function loadFoundationConfig(srcDir) {
 
   try {
     const module = await import(pathToFileURL(filePath).href)
+    warnMisplacedCapabilities(module, filePath)
     // Support both default export and named exports
     return {
       ...module.default,