Pre-bundle late-discovered deps so the dev worker never program-reloads mid-suite

vite was discovering effect/Match, effect/Predicate, and js-yaml during test
runs instead of at boot, forcing a re-optimize and full program reload on
both the client and SSR (workerd) environments. Each reload strands the
previous worker program's heap inside workerd, and a handful of them exhausts
its heap limit and kills the dev server mid-shard. Adding these to
optimizeDeps.include (client) and environments.ssr.optimizeDeps.include (SSR)
in apps/cloud and apps/host-selfhost's vite configs makes vite bundle them at
boot instead, so no mid-run discovery happens.

js-yaml is a transitive dependency via @executor-js/plugin-openapi that bun's
isolated install doesn't hoist into either app's node_modules, so a bare
"js-yaml" specifier silently fails to resolve in optimizeDeps.include. Used
vite's "<pkg> > <dep>" nested resolution syntax to resolve it from the
owning package instead.

Author: RhysSullivan

apps/cloud/vite.config.ts

@@ -65,6 +65,32 @@ export default defineConfig(({ command, mode }) => {
     delete (publicEnv as Record<string, string | undefined>).VITE_PUBLIC_OTLP_TRACES_URL;
   }
 
+  // Deps vite only discovers once a lazy-loaded React chunk actually renders
+  // (e.g. opening the MCP/OpenAPI "add source" flow). Discovering them mid-run
+  // forces a re-optimize + full program reload; in workerd (apps/cloud's SSR
+  // worker) each reload stacks a new isolate's heap on top of the last one
+  // without freeing it, so a handful of reloads exhausts the worker's heap
+  // limit and crashes the dev server. Pre-bundling them at boot means vite
+  // never discovers them mid-run, so it never reloads. Keep this list scoped
+  // to deps actually imported by UI code (grep `from "effect/` under
+  // packages/react/src and packages/plugins/*/src/react, plus js-yaml pulled
+  // in via packages/plugins/openapi/src/sdk) rather than including the world.
+  // js-yaml is a transitive dep (via @executor-js/plugin-openapi), not hoisted
+  // into apps/cloud/node_modules under bun's isolated install, so a plain
+  // "js-yaml" specifier fails to resolve here and silently falls out of the
+  // pre-bundle. The "<pkg> > <dep>" syntax resolves it starting from that
+  // package's own node_modules instead.
+  const lateDiscoveredDeps = [
+    "effect/Match",
+    "effect/Predicate",
+    "effect/Exit",
+    "effect/Option",
+    "effect/Cause",
+    "effect/Data",
+    "effect/Schema",
+    "@executor-js/plugin-openapi > js-yaml",
+  ];
+
   return {
     define: Object.fromEntries(
       Object.entries(publicEnv)
@@ -81,6 +107,22 @@ export default defineConfig(({ command, mode }) => {
       },
     },
     resolve: { tsconfigPaths: true },
+    // Client-side pre-bundle. See lateDiscoveredDeps comment above.
+    optimizeDeps: {
+      include: lateDiscoveredDeps,
+    },
+    // SSR/worker-side pre-bundle for the same deps, keyed under the "ssr"
+    // environment name that `cloudflare({ viteEnvironment: { name: "ssr" } })`
+    // below uses. The cloudflare plugin sets its own environments.ssr.optimizeDeps
+    // (entries/exclude for worker externals); vite merges include arrays rather
+    // than replacing them, so this only adds to that, it doesn't fight it.
+    environments: {
+      ssr: {
+        optimizeDeps: {
+          include: lateDiscoveredDeps,
+        },
+      },
+    },
     plugins: [
       devCrashGuard(),
       tailwindcss(),

apps/host-selfhost/vite.config.ts

@@ -190,6 +190,29 @@ export default defineConfig({
     alias: { "@executor-app": APP_ROOT },
     dedupe: ["react", "react-dom"],
   },
+  // This SPA shares packages/app's shell and packages/react's lazy-loaded
+  // "add source" UI with apps/cloud, so the same deps only surface once a
+  // lazy chunk actually renders (e.g. opening the MCP/OpenAPI add-source
+  // flow). Pre-bundle them at boot so vite never discovers them mid-run and
+  // never has to re-optimize + reload. No SSR/worker environment here (this
+  // app has no cloudflare plugin, it's a plain SPA build), so only the
+  // client optimizeDeps applies. Keep in sync with apps/cloud/vite.config.ts.
+  // js-yaml is a transitive dep (via @executor-js/plugin-openapi) that isn't
+  // hoisted into this app's node_modules under bun's isolated install, so a
+  // plain "js-yaml" specifier fails to resolve; "<pkg> > <dep>" resolves it
+  // from that package's own node_modules instead.
+  optimizeDeps: {
+    include: [
+      "effect/Match",
+      "effect/Predicate",
+      "effect/Exit",
+      "effect/Option",
+      "effect/Cause",
+      "effect/Data",
+      "effect/Schema",
+      "@executor-js/plugin-openapi > js-yaml",
+    ],
+  },
   define: {
     "import.meta.env.VITE_APP_VERSION": JSON.stringify(EXECUTOR_VERSION ?? "0.0.0"),
     // Self-host upgrades by pulling/rebuilding the image (or git + rebuild), not