@uniweb/build 1.3.1 → 1.3.3

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@uniweb/build",
-  "version": "1.3.1",
+  "version": "1.3.3",
   "description": "Build tooling for the Uniweb Component Web Platform",
   "type": "module",
   "exports": {
@@ -56,15 +56,15 @@
     "js-yaml": "^4.1.0",
     "sharp": "^0.35.3",
     "yaml": "^2.5.0",
-    "@uniweb/theming": "~1.2.0",
     "@uniweb/projections": "~1.1.1",
-    "@uniweb/content-reader": "~1.3.1",
-    "@uniweb/semantic-parser": "~1.7.0",
-    "@uniweb/schemas": "~1.2.1",
-    "@uniweb/content-writer": "~1.1.1"
+    "@uniweb/theming": "~1.2.0",
+    "@uniweb/semantic-parser": "~1.8.0",
+    "@uniweb/content-writer": "~1.1.2",
+    "@uniweb/schemas": "~1.3.0",
+    "@uniweb/content-reader": "~1.3.2"
   },
   "optionalDependencies": {
-    "@uniweb/runtime": "~1.1.2"
+    "@uniweb/runtime": "~1.1.3"
   },
   "peerDependencies": {
     "vite": "^5.0.0 || ^6.0.0 || ^7.0.0",
@@ -73,8 +73,8 @@
     "@tailwindcss/vite": "^4.0.0",
     "@vitejs/plugin-react": "^4.0.0 || ^5.0.0",
     "vite-plugin-svgr": "^4.0.0",
-    "@uniweb/core": "~1.2.1",
-    "@uniweb/runtime": "~1.1.2"
+    "@uniweb/core": "~1.2.2",
+    "@uniweb/runtime": "~1.1.3"
   },
   "peerDependenciesMeta": {
     "vite": {

package/src/foundation/config.js

@@ -26,6 +26,7 @@
 import { resolve } from 'node:path'
 import { foundationPlugin } from '../vite-foundation-plugin.js'
 import { jsxExtensionGuard } from '../jsx-extension.js'
+import { nodeEnvDefine } from './node-env.js'
 import { resolveFoundationSrcDir } from '../utils/foundation-source-root.js'
 // 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
@@ -36,6 +37,8 @@ import { resolveFoundationSrcDir } from '../utils/foundation-source-root.js'
 // cycle risk.
 import { DEFAULT_EXTERNALS } from '../import-map-plugin.js'
 
+export { nodeEnvDefine }
+
 /**
  * Create a complete Vite configuration for a Uniweb foundation
  *
@@ -110,6 +113,7 @@ export async function defineFoundationConfig(options = {}) {
     foundationPlugin({ srcDir, sections: sectionPaths }),
     // JSX compiles only in .jsx files: a .js file holding it fails with that said.
     jsxExtensionGuard(),
+    nodeEnvDefine(),
     tailwind && tailwindcss(),
     react(),
     svgr(),

package/src/foundation/node-env.js

@@ -0,0 +1,30 @@
+/**
+ * The `process.env.NODE_ENV` define a foundation build needs — a leaf, so the
+ * browser build (`foundation/config.js`) and the SSR twin
+ * (`vite-foundation-plugin.js::buildEntrySSR`) share one definition.
+ */
+
+/**
+ * Replace `process.env.NODE_ENV` in the foundation bundle.
+ *
+ * Library mode replaces `import.meta.env.*` and deliberately leaves
+ * `process.env.*` alone, so a bundled CommonJS dependency that branches on
+ * `process.env.NODE_ENV` (common in the React ecosystem) ships the read as
+ * written — and a browser, which has no `process`, throws
+ * `ReferenceError: process is not defined` when the foundation loads, so the
+ * site renders nothing. A foundation is a browser module, never a library a
+ * consumer re-bundles, so the read is resolved here, from the build's mode.
+ *
+ * An author's own `define` for the key wins: it is left untouched.
+ */
+export function nodeEnvDefine() {
+  const KEY = 'process.env.NODE_ENV'
+  return {
+    name: 'uniweb:foundation-node-env',
+    config(config, { mode }) {
+      if (config.define && KEY in config.define) return
+      const value = mode === 'development' ? 'development' : 'production'
+      return { define: { [KEY]: JSON.stringify(value) } }
+    }
+  }
+}

package/src/uwx/data-schema.js

@@ -460,9 +460,9 @@ function lowerLeaf(field, resolve, optResolve, { multiple = false, path = '' } =
   if (field.label) out.label = field.label
   if (field.description) out.description = field.description
   if (field.required) out.required = true
-  // A field's rules, as written — `max_length`, `min`, `max`, `mime_types`, `max_size`
-  // (`FIELD_RULES`): a registry keeps each as the field's own key and checks it on every
-  // write. ⛔ Until 2026-10-15 the normalizer dropped them before this saw them.
+  // A field's rules, as written — `max_length`, `min`, `max`, `mime_types`, `max_size`,
+  // `pattern` (`FIELD_RULES`): a registry keeps each as the field's own key and checks it on
+  // every write. ⛔ Until 2026-10-15 the normalizer dropped them before this saw them.
   for (const key of Object.keys(FIELD_RULES)) {
     if (field[key] !== undefined) out[key] = field[key]
   }

package/src/vite-foundation-plugin.js

@@ -17,6 +17,7 @@ import { generateFoundationVars } from './theme/index.js'
 import { DEFAULT_EXTERNALS } from './import-map-plugin.js'
 import { deriveSupports } from './foundation/derive-supports.js'
 import { proseWithoutStyles, PROSE_WITHOUT_STYLES_WARNING } from './foundation/prose-styles.js'
+import { nodeEnvDefine } from './foundation/node-env.js'
 
 // Foundations already told that their prose has no stylesheet — once per process, so a dev
 // server's rebuild on every save does not repeat it.
@@ -347,7 +348,7 @@ async function buildEntrySSR(foundationRoot, entrySourcePath, outDir) {
     }
     const react = (await import('@vitejs/plugin-react')).default
     const svgr = (await import('vite-plugin-svgr')).default
-    plugins.push(react(), svgr())
+    plugins.push(react(), svgr(), nodeEnvDefine())
 
     await viteBuild({
       root: foundationRoot,