@uniweb/build 0.18.0 → 0.18.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@uniweb/build",
-  "version": "0.18.0",
+  "version": "0.18.2",
   "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/schemas": "0.2.10",
     "@uniweb/theming": "0.1.15",
     "@uniweb/content-writer": "0.3.3",
+    "@uniweb/schemas": "0.2.10",
     "@uniweb/projections": "0.2.5"
   },
   "optionalDependencies": {
     "@uniweb/content-reader": "1.2.2",
     "@uniweb/schemas": "0.2.10",
-    "@uniweb/runtime": "0.11.0",
+    "@uniweb/runtime": "0.11.2",
     "@uniweb/semantic-parser": "1.2.1"
   },
   "peerDependencies": {

package/src/foundation/config.js

@@ -26,23 +26,14 @@
 import { resolve } from 'node:path'
 import { foundationPlugin } from '../vite-foundation-plugin.js'
 import { resolveFoundationSrcDir } from '../utils/foundation-source-root.js'
-
-/**
- * Default externals for foundations
- * These are not bundled into the foundation output
- */
-/**
- * Default externals for foundations
- * These are provided by the runtime and should not be bundled
- */
-const DEFAULT_EXTERNALS = [
-  'react',
-  'react-dom',
-  'react-dom/server',
-  'react/jsx-runtime',
-  'react/jsx-dev-runtime',
-  '@uniweb/core'
-]
+// The ONE definition. This list used to be re-typed here, and again in
+// vite-foundation-plugin.js — three hand-synced copies of "what a foundation
+// externalizes", with nothing binding them. The failure mode of a drift is not
+// a build error: it is the same bare specifier resolving to two React
+// instances at runtime, which breaks hooks with no signal at build time.
+// `import-map-plugin.js` imports nothing, so this is a leaf import with no
+// cycle risk.
+import { DEFAULT_EXTERNALS } from '../import-map-plugin.js'
 
 /**
  * Create a complete Vite configuration for a Uniweb foundation

package/src/vite-foundation-plugin.js

@@ -14,6 +14,7 @@ import { buildSchema } from './schema.js'
 import { generateEntryPoint, shouldRegenerateForFile } from './generate-entry.js'
 import { processAllPreviews } from './images.js'
 import { generateFoundationVars } from './theme/index.js'
+import { DEFAULT_EXTERNALS } from './import-map-plugin.js'
 
 /**
  * Build schema.json with preview image references
@@ -358,11 +359,12 @@ async function emitFoundationVarsCss(outDir, schema) {
 /**
  * Externals for the SSR bundle (`dist/entry-ssr.js`).
  *
- * Same set the browser foundation build externalizes (DEFAULT_EXTERNALS in
- * foundation/config.js — react/react-dom/react-dom-server/jsx-runtime/core),
- * which the Cloudflare edge isolate resolves to the SHARED runtime's React/core
- * (worker-runtime.js) via its shims — so React stays deduped and runtime patches
- * still propagate without a foundation rebuild.
+ * Same set the browser foundation build externalizes, and now literally the
+ * same array — `DEFAULT_EXTERNALS`, imported rather than re-typed. The isolate
+ * resolves these to the SHARED runtime's React/core (worker-runtime.js) via its
+ * shims, so React stays deduped and runtime patches still propagate without a
+ * foundation rebuild. "Same set" was a comment three copies made a promise
+ * rather than a fact; deriving it makes drift unrepresentable.
  *
  * PLUS the client-only libraries kit code-splits via dynamic import:
  *   - shiki / shiki/bundle/full — syntax highlighting (kit Code renderer)
@@ -372,14 +374,7 @@ async function emitFoundationVarsCss(outDir, schema) {
  * the SSR bundle and leaves them as DORMANT dynamic imports the isolate never
  * awaits — so no extra modules-map entry is needed for them edge-side.
  */
-const SSR_DEFAULT_EXTERNALS = [
-  'react',
-  'react-dom',
-  'react-dom/server',
-  'react/jsx-runtime',
-  'react/jsx-dev-runtime',
-  '@uniweb/core',
-]
+const SSR_DEFAULT_EXTERNALS = DEFAULT_EXTERNALS
 
 function isSSRExternal(id) {
   if (SSR_DEFAULT_EXTERNALS.includes(id)) return true