@abide/abide 0.43.0 → 0.44.0

package/src/serverBuildPlugins.ts

@@ -1,12 +1,14 @@
 import type { BunPlugin } from 'bun'
 import { abideResolverPlugin } from './abideResolverPlugin.ts'
 import { abideUiPlugin } from './lib/ui/compile/abideUiPlugin.ts'
+import { zodCjsPlugin } from './zodCjsPlugin.ts'
 
 /*
-The server-target Bun.build plugin pair shared by compile / buildCli / bundleApp:
-the abide-ui `.abide` loader (so SSR `render()` resolves) plus abide's virtual-
-module resolver. `embedAssets` flips on the gzip asset embed used by the
-standalone server binary; the CLI + launcher builds leave it off.
+The server-target Bun.build plugin set shared by compile / buildCli / bundleApp:
+the abide-ui `.abide` loader (so SSR `render()` resolves), abide's virtual-module
+resolver, and the zod→CommonJS shim that works around bun's broken ESM-cycle
+bundling (see zodCjsPlugin). `embedAssets` flips on the gzip asset embed used by
+the standalone server binary; the CLI + launcher builds leave it off.
 */
 export function serverBuildPlugins({
     cwd,
@@ -15,5 +17,9 @@ export function serverBuildPlugins({
     cwd: string
     embedAssets?: boolean
 }): BunPlugin[] {
-    return [abideUiPlugin, abideResolverPlugin({ cwd, embedAssets, target: 'server' })]
+    return [
+        zodCjsPlugin(cwd),
+        abideUiPlugin,
+        abideResolverPlugin({ cwd, embedAssets, target: 'server' }),
+    ]
 }

package/src/zodCjsPlugin.ts

@@ -0,0 +1,36 @@
+import { existsSync } from 'node:fs'
+import { dirname } from 'node:path'
+import type { BunPlugin } from 'bun'
+
+/*
+Routes every `zod` import in a server bundle to zod's CommonJS build.
+
+zod v4's ESM is reached through two subpaths (`zod` and `zod/v4/core`) whose
+modules form an initialization cycle. Bun's bundler emits a broken init order
+for that cycle (oven-sh/bun#31586, closed as not-planned), so a bundled binary
+crashes (`<helper> is not defined`) or — for a lazily imported module — silently
+fails to evaluate, which drops every rpc whose module imports zod from the
+registry. It only bites bundled output; `abide dev` runs unbundled and is fine.
+
+zod ships a parallel CommonJS build (`index.cjs`, `v4/core/index.cjs`, …), and
+CommonJS resolves circular requires through a mutating `module.exports` with no
+temporal-dead-zone, so the cycle initializes correctly. Resolving each zod
+specifier to its `.cjs` sibling makes bun bundle zod as CommonJS and sidesteps
+the bug while keeping zod v4. Server-only: the client bundle strips zod from rpc
+modules (they become remote proxies), and dev never bundles.
+*/
+export function zodCjsPlugin(cwd: string): BunPlugin {
+    return {
+        name: 'abide-zod-cjs',
+        setup(build) {
+            build.onResolve({ filter: /^zod($|\/)/ }, (args) => {
+                /* Resolve from the importer (or cwd for the entry) to zod's ESM
+                   target, then swap to its `.cjs` sibling when one exists. */
+                const from = args.importer ? dirname(args.importer) : cwd
+                const resolved = Bun.resolveSync(args.path, from)
+                const cjs = resolved.replace(/\.js$/, '.cjs')
+                return { path: existsSync(cjs) ? cjs : resolved }
+            })
+        },
+    }
+}

package/template/.zed/settings.json

@@ -1,4 +1,10 @@
 {
   "auto_install_extensions": { "abide": true },
-  "semantic_tokens": "combined"
+  "semantic_tokens": "combined",
+  "global_lsp_settings": {
+    "semantic_token_rules": [
+      { "token_type": "tag", "style": ["tag"] },
+      { "token_type": "attribute", "style": ["attribute"] }
+    ]
+  }
 }

package/template/package.json

@@ -14,5 +14,8 @@
     },
     "dependencies": {
         "@abide/abide": "^0.27.0"
+    },
+    "devDependencies": {
+        "@types/bun": "^1.3.14"
     }
 }

package/template/src/ui/pages/layout.abide

@@ -1,8 +1,8 @@
 <script>
 /*
 Root layout. A layout.abide wraps every page at or below its folder — here
-src/ui/pages/, so it wraps the whole app. The page lands in the <slot/> outlet;
-the resolver finds it by filename (no per-page import), and the client router
+src/ui/pages/, so it wraps the whole app. The page renders where this layout
+calls {children()}; the resolver finds it by filename (no per-page import), and the client router
 keeps it mounted across navigation, so this chrome never re-mounts. A nested
 layout.abide (in a subfolder) wraps inside this one. Runs on the server during
 SSR and on the client after hydration.
@@ -16,6 +16,4 @@ import '../app.css'
         <a href="/about">About</a>
     </nav>
 </header>
-<main>
-    <slot></slot>
-</main>
+<main>{children()}</main>