@uniweb/build 0.15.1 → 0.15.3

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@uniweb/build",
-  "version": "0.15.1",
+  "version": "0.15.3",
   "description": "Build tooling for the Uniweb Component Web Platform",
   "type": "module",
   "exports": {
@@ -63,7 +63,7 @@
     "@uniweb/content-writer": "0.2.7"
   },
   "optionalDependencies": {
-    "@uniweb/runtime": "0.8.33",
+    "@uniweb/runtime": "0.8.34",
     "@uniweb/content-reader": "1.1.15",
     "@uniweb/schemas": "0.2.4"
   },

package/src/site/build-site-data.js

@@ -51,9 +51,12 @@ import { generateCollectionIndex } from '../search/collections.js'
  *   - `_pages/<route>.json` — only meaningful for static-host bundles
  *     where they're served as static assets. Worker derives them from
  *     `payload.locales[lang].pages[].sections` server-side.
- *   - `sitemap.xml`, `robots.txt`, `search-index.json` — worker generates
- *     sitemap/robots at request time; search-index is currently
- *     bundle-mode-only territory.
+ *   - `sitemap.xml`, `robots.txt` — static-host bundle territory. Note these
+ *     are simply absent from Uniweb-hosted sites today: nothing in platform
+ *     generates them, at publish time or at request time.
+ *   - `search-index.json` — the single-file bundle-mode form. Link mode emits
+ *     the split `_search/{locale}/*.json` files instead (step 5 below), gated
+ *     by `features: [search]`; those are what the hosting worker serves.
  *
  * @param {Object} params
  * @param {string} params.siteRoot - Absolute path to the site directory.

package/src/site/config.js

@@ -263,12 +263,18 @@ export function readIntelligenceConfig(siteRoot) {
  * @param {string} [options.base] - Base public path for deployment (e.g., '/demos/mysite/')
  * @returns {Promise<Object>} Vite configuration
  */
+/** De-duplicate a list, keeping first-seen order. */
+function unique(list) {
+  return [...new Set(list)]
+}
+
 export async function defineSiteConfig(options = {}) {
   const {
     plugins: extraPlugins = [],
     server: serverOverrides = {},
     build: buildOverrides = {},
     resolve: resolveOverrides = {},
+    optimizeDeps: optimizeDepsOverrides = {},
     seo = {},
     assets = {},
     search = {},
@@ -575,9 +581,21 @@ export async function defineSiteConfig(options = {}) {
       ...buildOverrides
     },
 
+    // `include` and `exclude` are unioned with anything the site adds rather
+    // than replaced by it. Every other key here is a value a caller can
+    // reasonably want to override outright; these two are lists of things that
+    // must be true, and the framework's entries are load-bearing — React has to
+    // be prebundled or the site gets two copies of it. A site adding one
+    // package to `exclude` is asking for one more exclusion, not volunteering
+    // to restate the framework's list, and getting that wrong is silent: the
+    // dev server starts, and the failure surfaces somewhere unrelated.
     optimizeDeps: {
-      include: ['react', 'react-dom', 'react-dom/client', 'react-dom/server', 'react-router-dom'],
-      exclude: ['#foundation']
+      ...optimizeDepsOverrides,
+      include: unique([
+        'react', 'react-dom', 'react-dom/client', 'react-dom/server', 'react-router-dom',
+        ...(optimizeDepsOverrides.include || [])
+      ]),
+      exclude: unique(['#foundation', ...(optimizeDepsOverrides.exclude || [])])
     },
 
     ...restOptions