@octanejs/vite-plugin 0.1.10 → 0.1.12

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@octanejs/vite-plugin",
-  "version": "0.1.10",
+  "version": "0.1.12",
   "license": "MIT",
   "type": "module",
   "engines": {
@@ -46,18 +46,18 @@
     }
   },
   "dependencies": {
-    "@ripple-ts/adapter": "^0.3.86",
-    "@octanejs/app-core": "0.0.6"
+    "@ripple-ts/adapter": "^0.3.101",
+    "@octanejs/app-core": "0.0.8"
   },
   "peerDependencies": {
     "vite": "^8.0.16",
-    "octane": "0.1.10"
+    "octane": "0.1.12"
   },
   "devDependencies": {
     "@types/node": "^24.3.0",
     "playwright": "^1.61.0",
     "type-fest": "^5.6.0",
     "vite": "^8.0.16",
-    "octane": "0.1.10"
+    "octane": "0.1.12"
   }
 }

package/src/index.js

@@ -210,9 +210,9 @@ function collect_hydrate_module_paths(config) {
  * build is redirected to `{outDir}/client` with a manifest, the hydrate entry
  * is injected into index.html (so Vite bundles + hashes it), and closeBundle
  * runs a second, `ssr: true` build of a generated server entry to
- * `{outDir}/server/entry.js` — a self-contained module (app + octane bundled,
- * node builtins external) exporting `handler`/`nodeHandler` and auto-booting
- * under `node`. See server/virtual-entry.js and server/production.js.
+ * `{outDir}/server/entry.js`. Node-target adapters get the existing bootable
+ * `handler`/`nodeHandler` module; webworker-target adapters get an importable
+ * `createWebWorkerHandler` factory for their deployment wrapper.
  *
  * @param {{ hmr?: boolean, profile?: boolean, exclude?: string[], requireDirective?: boolean, renderers?: import('@octanejs/app-core').ExperimentalRendererConfigOptions }} [inlineOptions]
  * @returns {Plugin[]}
@@ -670,6 +670,7 @@ export function octane(inlineOptions = {}) {
 		async closeBundle() {
 			if (!isBuild || isSSRBuild || !has_route_config(buildOctaneConfig)) return;
 			const cfg = /** @type {ResolvedOctaneConfig} */ (buildOctaneConfig);
+			const webWorkerServer = cfg.adapter?.serverTarget === 'webworker';
 
 			console.log('[@octanejs/vite-plugin] Client build done. Building the server bundle…');
 
@@ -712,9 +713,11 @@ export function octane(inlineOptions = {}) {
 					rootBoundary: cfg.rootBoundary,
 					rpcModulePaths: [...serverModuleModules],
 					clientAssetMap,
+					...(webWorkerServer ? { mode: 'webworker' } : null),
 					// The virtual entry has no filesystem importer, so resolve app-core
 					// from this package before handing source to Vite. This also works
 					// when app-core is nested under the plugin by a package manager.
+					configModuleId: requireFromPlugin.resolve('@octanejs/app-core/config'),
 					productionModuleId: requireFromPlugin.resolve('@octanejs/app-core/production'),
 					nodeModuleId: requireFromPlugin.resolve('@octanejs/app-core/node'),
 				}),
@@ -739,6 +742,10 @@ export function octane(inlineOptions = {}) {
 			await viteBuild({
 				root,
 				appType: 'custom',
+				// Vite deliberately preserves process.env references in SSR/library
+				// output. Pin build intent here so Rollup can remove Octane's complete
+				// development error table even when the server bundle is not minified.
+				define: { 'process.env.NODE_ENV': JSON.stringify('production') },
 				plugins: [virtualEntryPlugin],
 				resolve: {
 					alias: [
@@ -760,6 +767,10 @@ export function octane(inlineOptions = {}) {
 					minify: cfg.build.minify ?? false,
 					rollupOptions: {
 						input: VIRTUAL_SERVER_ENTRY_ID,
+						// Cloudflare's nodejs_compat exposes `node:` modules directly.
+						// Preserve application imports as well as Octane's current runtime
+						// dependencies instead of replacing them with browser shims.
+						...(webWorkerServer ? { external: [/^node:/] } : null),
 						output: {
 							entryFileNames: ENTRY_FILENAME,
 							format: 'esm',
@@ -767,6 +778,7 @@ export function octane(inlineOptions = {}) {
 					},
 				},
 				ssr: {
+					...(webWorkerServer ? { target: 'webworker' } : null),
 					// Self-contained server bundle: everything except node builtins is
 					// bundled, so dist/server deploys without node_modules. 'vite'
 					// stays external as a guard — nothing should reach it (the facade
@@ -784,9 +796,11 @@ export function octane(inlineOptions = {}) {
 			}
 
 			console.log(`[@octanejs/vite-plugin] Server build complete: ${path.join(outDir, 'server')}`);
-			console.log(
-				`[@octanejs/vite-plugin] Start with: node ${outDir}/server/${ENTRY_FILENAME} (or octane-preview)`,
-			);
+			if (!webWorkerServer) {
+				console.log(
+					`[@octanejs/vite-plugin] Start with: node ${outDir}/server/${ENTRY_FILENAME} (or octane-preview)`,
+				);
+			}
 
 			// ------------------------------------------------------------------
 			// Deploy adapter (SvelteKit-style): with both bundles on disk, let the

package/src/server/render-route.js

@@ -266,7 +266,7 @@ pre { background: #2d2d2d; padding: 1rem; border-radius: 4px; overflow-x: auto;
 </head>
 <body>
 <h1>SSR Render Error</h1>
-<p class="route">Route: ${route.path} → ${route.entry}</p>
+<p class="route">Route: ${route.path} → ${get_route_entry_path(route.entry)}</p>
 <pre>${escapeHtml(message)}</pre>
 ${stack ? `<pre>${escapeHtml(stack)}</pre>` : ''}
 </body>

package/types/index.d.ts

@@ -23,13 +23,15 @@ export interface OctanePluginOptions {
 	 */
 	exclude?: string[];
 	/**
-	 * Mixed-toolchain ownership gate: when `true`, Octane compiles only
-	 * project modules that declare `'use octane'` in their directive prologue.
-	 * Undirected project `.tsx`/`.ts`/`.js` pass through to the host
-	 * framework's own pipeline (e.g. React's JSX transform); an undirected
-	 * project `.tsrx` is a build error. Installed and linked packages keep
-	 * their Octane package-manifest decision. The directive is always
-	 * tolerated and stripped from compiled output, even when this is off.
+	 * Mixed-toolchain ownership gate: when `true`, a project `.tsrx` is
+	 * Octane's by extension, and a project `.tsx` (full compile) or plain
+	 * `.ts`/`.js` (hook slotting) is Octane's only when it opens with a
+	 * leading `@jsxImportSource octane` pragma comment (any registered
+	 * renderer's intrinsics module also counts). A pragma naming a
+	 * foreign source (e.g. `react`) does not claim the file. Unmarked
+	 * project modules pass through to the host framework's own pipeline
+	 * (e.g. React's JSX transform). Installed and linked packages keep
+	 * their Octane package-manifest decision.
 	 * @default false
 	 */
 	requireDirective?: boolean;