@uniweb/build 0.44.1 → 0.44.3

package/README.md

@@ -324,11 +324,15 @@ After building, your foundation will contain:
 
 ```
 dist/
-├── foundation.js      # Bundled components (~6KB typical)
-├── foundation.js.map  # Source map
+├── entry.js           # The foundation — section types, layouts, declarations
+├── entry.js.map       # Source map
+├── entry-ssr.js       # Single-file twin of entry.js, for server-side prerender
+├── runtime-pin.json   # The @uniweb/runtime version it was built against
+├── *.js               # Code-split chunks, when the foundation has any
+├── assets/            # Styles and static assets
 └── meta/              # Editor metadata (not needed at runtime)
     ├── schema.json    # Full component metadata for editors
-    └── previews/      # Preset preview images
+    └── previews/      # Preset preview images, when presets declare them
         └── Hero/
             └── default.webp
 ```
@@ -357,9 +361,9 @@ The `_self` object contains foundation-level metadata:
 | `name` | `package.json` | Foundation package name |
 | `version` | `package.json` | Foundation version |
 | `description` | `package.json` | Foundation description |
-| `vars` | `foundation.js` | CSS custom properties sites can override |
+| `vars` | `main.js` | CSS custom properties sites can override |
 
-Identity fields (`name`, `version`, `description`) come from the foundation's `package.json`. Configuration fields (`vars`, etc.) come from `src/foundation.js`.
+Identity fields (`name`, `version`, `description`) come from the foundation's `package.json`. Configuration fields (`vars`, etc.) come from the foundation's `main.js`.
 
 ## API Reference
 
@@ -370,7 +374,7 @@ Identity fields (`name`, `version`, `description`) come from the foundation's `p
 | `discoverComponents(srcDir)` | Discover all section types (folders with meta.js) |
 | `loadComponentMeta(componentDir)` | Load meta file for a component |
 | `loadPackageJson(srcDir)` | Load identity from package.json |
-| `loadFoundationConfig(srcDir)` | Load foundation.js configuration |
+| `loadFoundationConfig(srcDir)` | Load the foundation's `main.js` declarations. A leftover `foundation.js` with no `main.js` beside it throws |
 | `buildSchema(srcDir)` | Build complete schema object |
 
 ### Entry Generation
@@ -387,7 +391,7 @@ The generated `_entry.generated.js` file exports:
 |--------|-------------|
 | `components` | Object map of component name → React component |
 | Named exports | Each component exported by name (e.g., `Hero`, `Features`) |
-| `capabilities` | Custom Layout and props from `src/foundation.js` (or `null`) |
+| `capabilities` | Custom Layout and props from `main.js` (or `null`) |
 | `meta` | Runtime metadata extracted from component `meta.js` files |
 
 #### Runtime Metadata (`meta` export)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@uniweb/build",
-  "version": "0.44.1",
+  "version": "0.44.3",
   "description": "Build tooling for the Uniweb Component Web Platform",
   "type": "module",
   "exports": {
@@ -57,15 +57,15 @@
     "js-yaml": "^4.1.0",
     "sharp": "^0.35.3",
     "yaml": "^2.5.0",
-    "@uniweb/content-writer": "^0.3.4",
-    "@uniweb/semantic-parser": "^1.4.0",
-    "@uniweb/projections": "^0.5.13",
-    "@uniweb/theming": "^0.1.15",
+    "@uniweb/schemas": "^0.2.13",
     "@uniweb/content-reader": "^1.2.4",
-    "@uniweb/schemas": "^0.2.13"
+    "@uniweb/projections": "^0.6.0",
+    "@uniweb/theming": "^0.1.15",
+    "@uniweb/content-writer": "^0.3.4",
+    "@uniweb/semantic-parser": "^1.4.0"
   },
   "optionalDependencies": {
-    "@uniweb/runtime": "^0.19.3"
+    "@uniweb/runtime": "^0.19.4"
   },
   "peerDependencies": {
     "vite": "^5.0.0 || ^6.0.0 || ^7.0.0",
@@ -74,7 +74,7 @@
     "@tailwindcss/vite": "^4.0.0",
     "@vitejs/plugin-react": "^4.0.0 || ^5.0.0",
     "vite-plugin-svgr": "^4.0.0",
-    "@uniweb/core": "^0.24.2"
+    "@uniweb/core": "^0.24.3"
   },
   "peerDependenciesMeta": {
     "vite": {

package/src/foundation/derive-supports.js

@@ -133,6 +133,30 @@ function isResolveServiceCall(node) {
   return false
 }
 
+/**
+ * A `.isServiceEnabled(name)` call on anything.
+ *
+ * ⛔ **Its name argument is at index 0, not 1.** `resolveService(website, name)`
+ * passes the website first; the method form has already bound it as the
+ * receiver. Reading index 1 here would find `undefined`, fall to the blind
+ * branch, and under-report `uniweb.supports` with a warning nobody is watching
+ * for — which is why `derive-supports.test.js` asserts a foundation calling
+ * `isSubmitEnabled()` derives `submit`.
+ *
+ * ⭐ This is how every `@uniweb/kit` service predicate is seen: they compile to
+ * `website.isServiceEnabled('<name>')`, and kit is bundled into the foundation,
+ * so the literal survives the shake. One matcher covers all of them — the name
+ * is an argument, so the family does not grow a rule per service.
+ */
+function isServiceEnabledCall(node) {
+  return (
+    node.type === 'CallExpression' &&
+    node.callee?.type === 'MemberExpression' &&
+    !node.callee.computed &&
+    node.callee.property?.name === 'isServiceEnabled'
+  )
+}
+
 /** A `.isSearchEnabled()` call on anything. */
 function isSearchEnabledCall(node) {
   return (
@@ -164,6 +188,11 @@ function collectSurvivors(bundle) {
 /**
  * Derive the services this foundation reaches for.
  *
+ * Three call shapes are read, and two of them carry the name as an argument so
+ * they cover the open registry without a rule per service:
+ * `resolveService(website, name)`, `website.isServiceEnabled(name)` (what every
+ * `@uniweb/kit` predicate compiles to), and the two hand-written gates below.
+ *
  * @param {object} bundle - Rollup's bundle, as handed to `writeBundle`
  * @param {object} ctx - the Rollup plugin context (`this` in the hook)
  * @returns {{services: string[], blind: boolean, blindAt: string[]}}
@@ -191,9 +220,12 @@ export function deriveSupports(bundle, ctx) {
         services.add('search')
         return
       }
-      if (!isResolveServiceCall(node)) return
+      const isMethod = isServiceEnabledCall(node)
+      if (!isMethod && !isResolveServiceCall(node)) return
 
-      const arg = node.arguments?.[1]
+      // The name is argument 0 on the method (the website is the receiver) and
+      // argument 1 on the free function. Getting this wrong under-reports.
+      const arg = node.arguments?.[isMethod ? 0 : 1]
       if (typeof arg?.value === 'string') {
         services.add(arg.value)
       } else if (arg?.type === 'Identifier' && consts.has(arg.name)) {

package/src/i18n/index.js

@@ -23,7 +23,8 @@ import {
   translateRecordData,
   RECORDS_DIR
 } from './records.js'
-import { generateSearchIndex, isSearchEnabled } from '@uniweb/projections'
+import { generateSearchIndex } from '@uniweb/projections'
+import { searchDeclaredOn } from '../site/search-declared.js'
 
 // Free-form translation support
 import {
@@ -400,7 +401,7 @@ export async function buildLocalizedContent(siteRoot, options = {}) {
     outputs[locale] = { content: contentOutputPath }
 
     // Generate search index for this locale if search is enabled
-    if (generateSearchIndexes && isSearchEnabled(translated)) {
+    if (generateSearchIndexes && searchDeclaredOn(translated)) {
       const searchConfig = translated.config?.search || {}
       const searchIndex = generateSearchIndex(translated, {
         locale,

package/src/schema.js

@@ -184,7 +184,11 @@ export async function loadPackageJson(srcDir) {
 }
 
 /**
- * Load foundation-level config file (main.js, fallback foundation.js)
+ * Load the foundation's declarations from `src/main.js`.
+ *
+ * ⛔ There is no `foundation.js` fallback — the legacy name was removed
+ * 2026-09-05. A leftover `foundation.js` with no `main.js` beside it is
+ * REFUSED rather than ignored; see `loadFoundationConfig`.
  *
  * Contains foundation-wide configuration:
  * - vars: CSS custom properties sites can override
@@ -340,7 +344,30 @@ export async function loadFoundationConfig(srcDir) {
       break
     }
   }
-  if (!filePath) return {}
+  if (!filePath) {
+    // ⛔ A LEFTOVER `foundation.js` IS NOT "NO CONFIG", AND MUST NOT READ AS ONE.
+    //
+    // The legacy name was removed 2026-09-05 (`FOUNDATION_FILE_NAMES` is
+    // `main.js` alone). This line used to return `{}` here regardless — so a
+    // project that kept the old name built "successfully" with every
+    // declaration silently gone: no `vars`, no `defaultLayout`, no
+    // `defaultSection`, no `props`. That is the exact outcome the guard below
+    // refuses on the import-failure path, reached through a door it did not
+    // cover. Found 2026-09-10 checking two downstream projects before an update;
+    // one would have lost its default layout and its output-format declarations.
+    //
+    // ⇒ Throw, like the guard below, rather than warn: a build log is where a
+    // warning goes to be missed, and the fix is a one-file rename.
+    const legacy = join(srcDir, 'foundation.js')
+    if (existsSync(legacy)) {
+      throw new Error(
+        `${legacy} is no longer read — rename it to main.js.\n` +
+          `  A foundation's declarations (vars, defaultLayout, defaultSection, props, name) live in\n` +
+          `  main.js. Left as foundation.js, the build would continue with none of them.`,
+      )
+    }
+    return {}
+  }
 
   let module
   try {

package/src/site/config.js

@@ -244,6 +244,7 @@ export async function defineSiteConfig(options = {}) {
         const agreement = checkFoundationResolution({
           name: foundationInfo.name,
           generatedInto: srcDir,
+          generatedEntry: entryPath,
           siteRoot,
         })
         if (!agreement.ok) console.warn(`\n${agreement.message}\n`)

package/src/site/plugin.js

@@ -209,8 +209,9 @@ async function processDevSectionFetches(sections, fetchOptions) {
     }
   }
 }
-import { generateSearchIndex, isSearchEnabled, getSearchIndexFilename } from '@uniweb/projections'
+import { generateSearchIndex, getSearchIndexFilename } from '@uniweb/projections'
 import { mergeTranslations } from '../i18n/merge.js'
+import { searchDeclaredOn } from './search-declared.js'
 import { mountDevApi } from '../dev/api-mount.js'
 
 /*
@@ -1145,7 +1146,7 @@ export function siteContentPlugin(options = {}) {
         // Serve search-index.json in dev mode (supports locale prefixes)
         const searchIndexMatch = req.url.match(new RegExp(`^(?:\\/(${LOCALE_RE}))?\\/search-index\\.json$`))
         if (searchIndexMatch && siteContent) {
-          const searchEnabled = searchPluginConfig.enabled !== false && isSearchEnabled(siteContent)
+          const searchEnabled = searchPluginConfig.enabled !== false && searchDeclaredOn(siteContent)
           if (searchEnabled) {
             const searchConfig = siteContent.config?.search || {}
             const defaultLocale = resolveDefaultLocale(siteContent.config)
@@ -1511,7 +1512,7 @@ export function siteContentPlugin(options = {}) {
       }
 
       // Generate search index if enabled
-      const searchEnabled = searchPluginConfig.enabled !== false && isSearchEnabled(finalContent)
+      const searchEnabled = searchPluginConfig.enabled !== false && searchDeclaredOn(finalContent)
       if (searchEnabled) {
         const searchConfig = finalContent.config?.search || {}
         const defaultLocale = resolveDefaultLocale(finalContent.config)

package/src/site/search-declared.js

@@ -0,0 +1,34 @@
+/**
+ * Is search on for this site, as the AUTHOR declared it?
+ *
+ * ⭐ **The build's own decision about its own output.** Deliberately not
+ * `@uniweb/projections`': that package is a helper library — it derives
+ * artifacts from content and must not gate on a site setting. Deciding whether
+ * to generate is the caller's job *[Diego, 2026-09-10]*.
+ *
+ * ⛔ **The boolean form is why this is not a one-liner.**
+ * `config?.search?.enabled !== false` reads `false.enabled` when an author
+ * writes `search: false`, because optional chaining short-circuits on
+ * `null`/`undefined` only — so `undefined !== false` is `true` and the natural
+ * spelling of "off" still shipped a `search-index.json` carrying every page's
+ * text. On a static export that file is world-readable. `Website.isSearchEnabled`
+ * fixed the same expression in `@uniweb/core`; the copy in projections never got
+ * it and now needs none. Pinned by `tests/search-declared.test.js`.
+ *
+ * ⚖️ **Author tier only, and that is correct here.** A host's `services` block
+ * decides where queries are *answered* at render; it has no bearing on whether
+ * this build emits an index. The render-time question is
+ * `Website.isServiceEnabled('search')`.
+ *
+ * ⛔ **A leaf on purpose.** It lived in `site/plugin.js` for one commit, which
+ * made `i18n/index.js` import a 26-module Vite plugin to reach four lines — and
+ * put one future import in the other direction away from a cycle.
+ *
+ * @param {object} siteContent - parsed site content, or anything with `.config`
+ * @returns {boolean}
+ */
+export function searchDeclaredOn(siteContent) {
+  const search = siteContent?.config?.search
+  if (typeof search === 'boolean') return search
+  return search?.enabled !== false
+}

package/src/utils/foundation-resolution-check.js

@@ -59,7 +59,7 @@
  * consulted. That is the step whose answer we need.
  */
 
-import { existsSync, realpathSync } from 'node:fs'
+import { existsSync, readFileSync, realpathSync } from 'node:fs'
 import { dirname, join, parse } from 'node:path'
 
 /**
@@ -85,6 +85,50 @@ export function findPackageDir(name, fromDir) {
   }
 }
 
+/**
+ * Does Vite's resolution of this package land on the very file we generated?
+ *
+ * ⭐ **This is the question the check exists to ask.** Comparing DIRECTORIES
+ * asked a different one and got it wrong for the most common layout there is: a
+ * package rooted at `foundations/<x>/`, its entry generated into
+ * `foundations/<x>/src/`, and `main` pointing there. That is two directories and
+ * ONE file. Measured 2026-09-10 against every site of a ten-site project: the
+ * directory check fired for six — five healthy `src/` layouts, and the single
+ * genuine case, a pnpm `file:` dependency copied into the store, buried among
+ * them. The entry comparison leaves exactly that one.
+ * A warning that fires on healthy projects is the failure this module's own
+ * header warns against.
+ *
+ * ⛔ **True only when the match is PROVEN** — both files exist and realpath to
+ * one place. Any failure to resolve returns false, so the caller reports the
+ * directory disagreement rather than silencing it: a copy with no entry, or one
+ * carrying a stale entry of its own, is still caught.
+ *
+ * Follows what Vite reads for a bare specifier: `exports['.']` (a string, or its
+ * `import`/`default` condition), else `main`, else `index.js`.
+ */
+function resolvesToSameEntry(generatedEntry, packageDir) {
+  let pkg
+  try {
+    pkg = JSON.parse(readFileSync(join(packageDir, 'package.json'), 'utf8'))
+  } catch {
+    return false
+  }
+  const pick = (v) =>
+    typeof v === 'string' ? v : v && typeof v === 'object' ? pick(v.import ?? v.default) : null
+  const exp = pkg.exports
+  let rel = null
+  if (typeof exp === 'string') rel = exp
+  else if (exp && typeof exp === 'object') rel = pick('.' in exp ? exp['.'] : exp)
+  rel ??= typeof pkg.main === 'string' ? pkg.main : null
+  rel ??= 'index.js'
+  try {
+    return realpathSync(generatedEntry) === realpathSync(join(packageDir, rel))
+  } catch {
+    return false
+  }
+}
+
 /**
  * Compare where we generated the foundation entry against where vite will look.
  *
@@ -100,9 +144,11 @@ export function findPackageDir(name, fromDir) {
  * @param {string} args.name - the foundation's declared name (the bare specifier)
  * @param {string} args.generatedInto - the directory we wrote `_entry.generated.js` to
  * @param {string} args.siteRoot - where vite resolves the bare specifier from
+ * @param {string} [args.generatedEntry] - the entry file we wrote; defaults to
+ *   `_entry.generated.js` inside `generatedInto`
  * @returns {{ ok: true } | { ok: false, ours: string, theirs: string, message: string }}
  */
-export function checkFoundationResolution({ name, generatedInto, siteRoot }) {
+export function checkFoundationResolution({ name, generatedInto, siteRoot, generatedEntry }) {
   const theirsRaw = findPackageDir(name, siteRoot)
   if (!theirsRaw) return { ok: true }
 
@@ -118,6 +164,13 @@ export function checkFoundationResolution({ name, generatedInto, siteRoot }) {
 
   if (ours === theirs) return { ok: true }
 
+  // Two directories are not two foundations. When the package Vite reaches
+  // resolves to the entry file we generated, the build reads what we wrote —
+  // the `src/` layout, where the entry sits one level below the package root.
+  if (resolvesToSameEntry(generatedEntry ?? join(generatedInto, '_entry.generated.js'), theirsRaw)) {
+    return { ok: true }
+  }
+
   return {
     ok: false,
     ours,

package/src/uwx/site.js

@@ -852,7 +852,9 @@ function queriesNested(declarations, uuids = null) {
 // config is bound where the service is provisioned, and arrives here by `pull`.
 //
 // ⚖️ WHAT THESE ARE NOT. A site's OWN service declarations — `search:`, `submit:`,
-// `assistant:`, `tracking:` — stay top-level `info.*` keys and are untouched. Those
+// `assistant:`, `tracking:` — ride the `settings` Section and are untouched here.
+// (They were top-level `info.*` keys until 2026-09-09; `settingsNested` below is
+// where they are now written.) Those
 // are authored, they resolve at the SITE tier (`config.<name>`, first choice in
 // `@uniweb/core`'s `resolveService`), and moving them here would flip them to the
 // host tier, where a block's mere presence declines every service it does not name.