@uniweb/build 0.80.3 → 0.80.4

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@uniweb/build",
-  "version": "0.80.3",
+  "version": "0.80.4",
   "description": "Build tooling for the Uniweb Component Web Platform",
   "type": "module",
   "exports": {
@@ -53,19 +53,19 @@
   },
   "dependencies": {
     "@citestyle/bibtex": "^1.1.0",
-    "esbuild": "^0.21.0 || ^0.23.0 || ^0.24.0 || ^0.25.0 || ^0.27.0",
+    "esbuild": "^0.21.0 || ^0.23.0 || ^0.24.0 || ^0.25.0 || ^0.27.0 || ^0.28.0",
     "js-yaml": "^4.1.0",
     "sharp": "^0.35.3",
     "yaml": "^2.5.0",
-    "@uniweb/projections": "^0.7.15",
-    "@uniweb/content-reader": "^1.2.8",
-    "@uniweb/content-writer": "^0.3.4",
-    "@uniweb/schemas": "^0.13.0",
-    "@uniweb/semantic-parser": "^1.5.1",
-    "@uniweb/theming": "^0.2.0"
+    "@uniweb/semantic-parser": "~1.5.1",
+    "@uniweb/theming": "~0.2.0",
+    "@uniweb/content-writer": "~0.3.4",
+    "@uniweb/schemas": "~0.13.0",
+    "@uniweb/content-reader": "~1.2.8",
+    "@uniweb/projections": "~0.7.16"
   },
   "optionalDependencies": {
-    "@uniweb/runtime": "^0.29.4"
+    "@uniweb/runtime": "~0.29.7"
   },
   "peerDependencies": {
     "vite": "^5.0.0 || ^6.0.0 || ^7.0.0",
@@ -74,8 +74,8 @@
     "@tailwindcss/vite": "^4.0.0",
     "@vitejs/plugin-react": "^4.0.0 || ^5.0.0",
     "vite-plugin-svgr": "^4.0.0",
-    "@uniweb/core": "^0.38.0",
-    "@uniweb/runtime": "^0.29.4"
+    "@uniweb/runtime": "~0.29.7",
+    "@uniweb/core": "~0.38.2"
   },
   "peerDependenciesMeta": {
     "vite": {

package/src/foundation/config.js

@@ -25,6 +25,7 @@
 
 import { resolve } from 'node:path'
 import { foundationPlugin } from '../vite-foundation-plugin.js'
+import { jsxExtensionGuard } from '../jsx-extension.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
@@ -107,6 +108,8 @@ export async function defineFoundationConfig(options = {}) {
   // foundationPlugin handles entry generation and schema building
   const plugins = [
     foundationPlugin({ srcDir, sections: sectionPaths }),
+    // JSX compiles only in .jsx files: a .js file holding it fails with that said.
+    jsxExtensionGuard(),
     tailwind && tailwindcss(),
     react(),
     svgr(),

package/src/jsx-extension.js

@@ -0,0 +1,68 @@
+/**
+ * JSX compiles only in `.jsx` and `.tsx` files — in a foundation's Vite build, in a
+ * site build that bundles its foundation, and in the step that reads `main.js`
+ * (`schema.js`, `importFoundationConfig`).
+ *
+ * ⭐ THE RULE, SAID WHERE IT FAILS. A `.js` file holding JSX fails each of those with a
+ * parser's message that never says why — Vite's "Expression expected", esbuild's "The JSX
+ * syntax extension is not currently enabled" — and section discovery accepts `.js`
+ * components, which build only without JSX. Ruled 2026-10-11: JSX stays in `.jsx` files,
+ * and the failure names the file and the fix.
+ */
+
+import { basename, relative } from 'node:path'
+
+const JS_FILE = /\.m?js$/
+
+/**
+ * What to tell an author whose `.js` file holds JSX — the rule and the fix, without the
+ * location, which each caller states its own way (Vite prefixes `file (line:col):`).
+ *
+ * @param {string} file - the file holding JSX
+ * @returns {string}
+ */
+export function jsxInJsMessage(file) {
+  const name = basename(file)
+  // `main.js` is the one name a foundation's declarations are read from, so it cannot
+  // become `main.jsx`: its components move out instead.
+  if (name === 'main.js') {
+    return 'JSX compiles only in .jsx and .tsx files, and main.js is plain JavaScript: move the component into a .jsx file and import it.'
+  }
+  return `JSX compiles only in .jsx and .tsx files — rename ${name} to ${name.replace(JS_FILE, '.jsx')}.`
+}
+
+/**
+ * A Vite plugin that turns a parse failure on JSX in a `.js` file into
+ * {@link jsxInJsMessage}. Silent otherwise: a file that parses, or fails for any other
+ * reason, is left to Vite. A file under `node_modules` is skipped — the advice is for files
+ * the author can rename.
+ *
+ * It parses only a project `.js` file that contains a `<`, and the failure it reports is the
+ * one the build would hit next: the parser stopped at that `<`.
+ *
+ * @returns {import('vite').Plugin}
+ */
+export function jsxExtensionGuard() {
+  let root = process.cwd()
+  return {
+    name: 'uniweb-jsx-extension',
+    enforce: 'pre',
+    configResolved(config) {
+      root = config.root
+    },
+    transform(code, id) {
+      const file = id.split('?')[0]
+      if (!JS_FILE.test(file) || file.includes('/node_modules/') || !code.includes('<')) return null
+      if (typeof this.parse !== 'function') return null
+      try {
+        this.parse(code)
+      } catch (error) {
+        const pos = error?.pos
+        if (typeof pos === 'number' && code[pos] === '<') {
+          this.error(jsxInJsMessage(relative(root, file)), pos)
+        }
+      }
+      return null
+    },
+  }
+}

package/src/schema.js

@@ -14,8 +14,9 @@ import { readdir, readFile, rm } from 'node:fs/promises'
 import { existsSync } from 'node:fs'
 import { createHash } from 'node:crypto'
 import { isFontVar } from '@uniweb/theming'
-import { join, dirname, extname, basename } from 'node:path'
+import { join, dirname, extname, basename, relative, resolve } from 'node:path'
 import { pathToFileURL } from 'node:url'
+import { jsxInJsMessage } from './jsx-extension.js'
 import { describeChildren, describeVisuals, lowerChildren } from '@uniweb/schemas/component'
 import { describeContent, lowerData } from '@uniweb/schemas/content'
 import { normalizeData, schemaDeclarationOf } from '@uniweb/schemas/foundation'
@@ -433,6 +434,16 @@ async function importFoundationConfig(filePath) {
         logLevel: 'silent',
       })
       return await import(`${pathToFileURL(outfile).href}?content=${content}`)
+    } catch (bundleError) {
+      // JSX in a `.js` file — `main.js` itself or a module it imports — compiles nowhere
+      // (jsx-extension.js): say so, rather than esbuild's "The JSX syntax extension is not
+      // currently enabled".
+      const jsx = bundleError?.errors?.find(
+        (e) => /JSX syntax extension/.test(e.text) && /\.m?js$/.test(e.location?.file ?? ''),
+      )
+      if (!jsx) throw bundleError
+      const file = relative(dirname(filePath), resolve(jsx.location.file))
+      throw new Error(`${file} (line ${jsx.location.line}): ${jsxInJsMessage(file)}`, { cause: bundleError })
     } finally {
       await rm(outfile, { force: true }).catch(() => {})
     }
@@ -482,13 +493,15 @@ export async function loadFoundationConfig(srcDir) {
       )
     }
     // ⛔ The same for `main.jsx`, which the entry used to import while this read nothing — the
-    // editor saw none of its declarations, the runtime all of them (until 2026-10-01). A main.js
-    // may hold JSX: `importFoundationConfig` transpiles it.
+    // editor saw none of its declarations, the runtime all of them (until 2026-10-01).
+    // ⛔ This said "rename it to main.js, which may hold JSX" until 2026-10-11, and main.js never
+    // could: JSX compiles only in .jsx files, here and in Vite (jsx-extension.js). A main.jsx's
+    // components move into a .jsx file the new main.js imports.
     const jsx = join(srcDir, 'main.jsx')
     if (existsSync(jsx)) {
       throw new Error(
-        `${jsx} is not read — rename it to main.js, which may hold JSX.\n` +
-          `  A foundation's declarations live in main.js; left as main.jsx, the build would continue with none of them.`,
+        `${jsx} is not read — rename it to main.js, and move any JSX it holds into a .jsx file it imports.\n` +
+          `  A foundation's declarations live in main.js, which is plain JavaScript; left as main.jsx, the build would continue with none of them.`,
       )
     }
     return {}

package/src/site/config.js

@@ -30,6 +30,7 @@ import {
   getStructuralWatchPaths
 } from '../generate-entry.js'
 import { importMapPlugin } from '../import-map-plugin.js'
+import { jsxExtensionGuard } from '../jsx-extension.js'
 import { resolveModuleUrl, resolveExtensionUrls } from './extension-urls.js'
 import { resolveFoundationSrcPath } from '../utils/foundation-source-root.js'
 import { checkFoundationResolution } from '../utils/foundation-resolution-check.js'
@@ -317,6 +318,8 @@ export async function defineSiteConfig(options = {}) {
     ensureFoundationEntryPlugin,
 
     // Standard plugins
+    // JSX compiles only in .jsx files — a bundled foundation's too.
+    jsxExtensionGuard(),
     tailwind && tailwindcss(),
     react(),
     svgr(),