@octanejs/vite-plugin 0.1.3 → 0.1.4

package/CHANGELOG.md

@@ -1,5 +1,77 @@
 # @octanejs/vite-plugin
 
+## 0.1.4
+
+### Patch Changes
+
+- 6d332ad: octane.config `adapter` is now the full deploy contract `{ name?, adapt?, serve?, runtime? }`: after the production server build, closeBundle runs `adapter.adapt({ root, outDir, clientDir, serverDir, log })` so an adapter package (e.g. `@octanejs/adapter-vercel`) can restructure the output for its platform (SvelteKit-style). All parts are optional and independent — `serve`/`runtime` keep their existing meanings. `@octanejs/adapter-vercel` is registered as a server-only package: client-side imports of it resolve to the browser stub (which now also covers the octane adapter surface, `vercel`/`adapt`) instead of dragging node builtins into the client graph.
+- 8fc8554: Production SSR builds — octane apps now deploy server-rendered instead of SPA-only:
+
+  - `vite build` produces BOTH bundles: hashed client assets in `{outDir}/client` (with the generated hydrate entry bundled into index.html via a static, Rollup-analyzable import map over the routes' entry/layout/preHydrate modules) and a self-contained SSR server at `{outDir}/server/entry.js` (app + octane bundled, only node builtins external; octane.config.ts is compiled in through a config-surface facade so neither the compiler nor vite ride along). The built index.html moves to `dist/server` — it is the SSR template, and leaving it in the static dir would shadow the handler at `/` on filesystem-first hosts.
+  - `createHandler` (`@octanejs/vite-plugin/production`) is implemented: it matches RenderRoutes/ServerRoutes, runs middleware chains, and streams via the same `renderToReadableStream` engine dev SSR uses — the rendered body region and the `#__octane_data` payload are byte-identical to dev, so `hydrateRoot()` adopts production responses unchanged (covered by an end-to-end fixture test). Per-route `<link rel="stylesheet">`/`modulepreload` tags come from the client manifest. `server.render: 'buffered'` in octane.config.ts switches to the await-everything `prerender` for hosts that break streamed responses.
+  - The server entry exports `handler` (Web fetch) and `nodeHandler` (Node `(req, res)`, for serverless wrappers such as a Vercel Node function), and auto-boots under `node dist/server/entry.js` — with the adapter's `serve()` when configured, else the new built-in Node server (`@octanejs/vite-plugin/node`) serving the client assets with immutable caching for `/assets/*`.
+  - `octane-preview` now runs that entry for real (pre-deploy verification) and accepts `--port`.
+
+- 3c56d95: Close the four metaframework gaps the octane website surfaced:
+
+  - `octane()` now accepts `exclude` and forwards it to the bundled compiler, so monorepo / aliased-to-source setups can skip the hook-slotting pass for hand-slot-forwarding binding sources (pnpm symlinks resolve `@octanejs/*` to `packages/*/src`, which the automatic node_modules skip can't see).
+  - The dev SSR middleware skips Vite-owned requests (`/@` namespaces, `/__` internals, node_modules, `?import`-style transform queries, and extension-bearing paths that name a real file under the Vite root/publicDir — dotted page URLs like `/docs/v2.0` still SSR) before route matching, so a catch-all `'/*splat'` RenderRoute can SSR a real not-found page without swallowing `/@vite/client` or `/src/*.ts`. `RenderRoute` also takes a `status` (e.g. 404 for the catch-all) applied to the rendered response.
+  - `appType: 'custom'` is now only a default: an explicit user `appType` wins, and `vite preview` is left on Vite's own SPA fallback so it can serve the client build (production SSR serving is still Phase 2).
+  - RenderRoute components (and layouts) receive the request `url` (pathname + search) alongside `params`, on the server and on the hydrating client, and the new `router.preHydrate` config names a module whose default export the client entry awaits before `hydrateRoot` — the hook an app-level client router uses to commit its match tree so hydration adopts the server DOM. The generated client entry also hides its dynamic imports from Vite's `?import` query injection so the page/hook share module singletons with statically-imported copies.
+
+  Dev SSR now streams: RenderRoutes render through `renderToReadableStream` (shell first, suspense boundaries flush out of order behind it) instead of the buffered `prerender`.
+
+- Updated dependencies [05fdef8]
+- Updated dependencies [e9ebfbf]
+- Updated dependencies [4ac4c98]
+- Updated dependencies [c2129eb]
+- Updated dependencies [4ac4c98]
+- Updated dependencies [8a44bb5]
+- Updated dependencies [6b0c244]
+- Updated dependencies [d3cf678]
+- Updated dependencies [05fdef8]
+- Updated dependencies [d19d4f3]
+- Updated dependencies [7e84258]
+- Updated dependencies [2f8c6ed]
+- Updated dependencies [8de4584]
+- Updated dependencies [9be6ba5]
+- Updated dependencies [db409de]
+- Updated dependencies [4f3c6c8]
+- Updated dependencies [62c3c4e]
+- Updated dependencies [3c56d95]
+- Updated dependencies [4c5b1d0]
+- Updated dependencies [b732399]
+- Updated dependencies [6d27cb0]
+- Updated dependencies [a3784b1]
+- Updated dependencies [fa77edf]
+- Updated dependencies [f5c9dba]
+- Updated dependencies [12d5410]
+- Updated dependencies [d71f1fc]
+- Updated dependencies [2f8c6ed]
+- Updated dependencies [63e51e8]
+- Updated dependencies [6d3b269]
+- Updated dependencies [b171c6d]
+- Updated dependencies [7f3d9c9]
+- Updated dependencies [820baaf]
+- Updated dependencies [c36cb32]
+- Updated dependencies [c33f409]
+- Updated dependencies [63e51e8]
+- Updated dependencies [8fc8554]
+- Updated dependencies [569daad]
+- Updated dependencies [6b7b727]
+- Updated dependencies [2ce7bc5]
+- Updated dependencies [c6a23f5]
+- Updated dependencies [c93aad5]
+- Updated dependencies [2942afb]
+- Updated dependencies [388b23c]
+- Updated dependencies [352cff1]
+- Updated dependencies [c7989eb]
+- Updated dependencies [dda2854]
+- Updated dependencies [dda2854]
+- Updated dependencies [3a9d855]
+- Updated dependencies [1f85217]
+  - octane@0.1.4
+
 ## 0.1.3
 
 ### Patch Changes
@@ -43,7 +115,7 @@
 ### Patch Changes
 
 - b3a9191: Rename `hydrate` → `hydrateRoot` and adopt React 18's shape. The hydration entry is now `hydrateRoot(container, <App/>)` — container first — and returns a full `Root` (with `.render()` and `.unmount()`), symmetric with `createRoot`. Previously `hydrate(Component, container, props)` put the component first and returned only `{ unmount }`. After hydration the returned root's `.render()` performs a normal client update against the adopted DOM (no re-hydration). The vite-plugin's generated client entry now imports and calls `hydrateRoot`.
-- 43d940d: Exclude `@octanejs/query` from esbuild pre-bundling (optimizeDeps.exclude + ssr.noExternal). It ships a `.tsrx` provider component, so — like `octane` itself — its source must flow through the octane `.tsrx` transform rather than being pre-bundled by esbuild.
+- 43d940d: Exclude `@octanejs/tanstack-query` from esbuild pre-bundling (optimizeDeps.exclude + ssr.noExternal). It ships a `.tsrx` provider component, so — like `octane` itself — its source must flow through the octane `.tsrx` transform rather than being pre-bundled by esbuild.
 - cb9ad82: Rename the project from `vyre` to `octane`. The runtime now publishes as `octane` and the Vite metaframework plugin as `@octanejs/vite-plugin`. Identifiers inherited from the Ripple fork were also renamed to Octane (e.g. `setIsRippleActEnvironment` → `setIsOctaneActEnvironment`, the metaframework `ripple()` plugin → `octane()`, and the `ripple.config.ts` convention → `octane.config.ts`). References to the upstream Ripple framework and its `@ripple-ts`/`@tsrx` packages are unchanged.
 - fcac573: Unify the server-rendering ABI to props-first, matching the client. A component body is now invoked as `(props, scope, extra)` on the server (it used to be `(scope, props, extra)`). This makes a plain `function Foo(props)` used at a `<Foo/>` site work the same on the server as on the client — including components that return a non-JSX value (a primitive coerced to text, an early return, `null`). SSR markup is unchanged (only the invocation order flipped), so hydration is unaffected. The server layout/page wrappers in the vite-plugin were updated to match.
 - 634fd52: Align the SSR API with React and reshape the render result to `{ html, css }`.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@octanejs/vite-plugin",
-  "version": "0.1.3",
+  "version": "0.1.4",
   "license": "MIT",
   "type": "module",
   "description": "Vite metaframework plugin for the octane renderer (dev SSR + routing + hydrate)",
@@ -31,11 +31,16 @@
       "types": "./types/production.d.ts",
       "import": "./src/server/production.js",
       "default": "./src/server/production.js"
+    },
+    "./node": {
+      "types": "./types/node.d.ts",
+      "import": "./src/server/node-http.js",
+      "default": "./src/server/node-http.js"
     }
   },
   "dependencies": {
     "@ripple-ts/adapter": "^0.3.86",
-    "octane": "0.1.3"
+    "octane": "0.1.4"
   },
   "devDependencies": {
     "@types/node": "^24.3.0",

package/src/bin/preview.js

@@ -1,13 +1,13 @@
 #!/usr/bin/env node
+// @ts-check
 
 /**
  * octane-preview — Start the production SSR server.
  *
- * Loads octane.config.ts, reads `build.outDir`,
- * and spawns `node {outDir}/server/entry.js`.
- *
- * NOTE: the server entry it spawns is produced by the Phase 2 production
- * build. Until then this validates existence and errors clearly.
+ * Loads octane.config.ts, reads `build.outDir`, and spawns
+ * `node {outDir}/server/entry.js` — the self-contained server bundle
+ * `vite build` produced. This is the pre-deploy verification step: the exact
+ * handler + static assets a production host runs, on localhost.
  */
 
 import { spawn } from 'node:child_process';
@@ -18,6 +18,20 @@ import { ENTRY_FILENAME } from '../constants.js';
 
 const projectRoot = process.cwd();
 
+// `--port <n>` / `-p <n>` sets the port (else $PORT, else the entry's 3000
+// default). `--strictPort` is accepted for `vite preview` muscle-memory and
+// ignored — the port is always exact (the entry never probes for a free one).
+/** @type {string | undefined} */
+let portArg;
+const args = process.argv.slice(2);
+for (let i = 0; i < args.length; i++) {
+	if (args[i] === '--port' || args[i] === '-p') {
+		portArg = args[++i];
+	} else if (args[i].startsWith('--port=')) {
+		portArg = args[i].slice('--port='.length);
+	}
+}
+
 try {
 	const config = await loadOctaneConfig(projectRoot);
 	const outDir = config.build.outDir;
@@ -34,6 +48,7 @@ try {
 	const child = spawn(process.execPath, [entryPath], {
 		stdio: 'inherit',
 		cwd: projectRoot,
+		env: portArg ? { ...process.env, PORT: portArg } : process.env,
 	});
 
 	child.on('close', (code) => {

package/src/config-entry.js

@@ -0,0 +1,31 @@
+// @ts-check
+/**
+ * Config-surface facade for the PRODUCTION server bundle.
+ *
+ * octane.config.ts imports `RenderRoute` / `ServerRoute` / `defineConfig` from
+ * '@octanejs/vite-plugin'. The real package entry (`src/index.js`) also pulls
+ * in the octane compiler, the dev-SSR middleware, and a dynamic `import('vite')`
+ * — none of which belong in dist/server/entry.js. The SSR sub-build therefore
+ * aliases the BARE '@octanejs/vite-plugin' specifier to this module, which
+ * re-exports only what a config file can legitimately use. Subpath imports
+ * ('@octanejs/vite-plugin/production', '/node') are not affected by the alias.
+ */
+
+export { RenderRoute, ServerRoute } from './routes.js';
+export { resolveOctaneConfig } from './resolve-config.js';
+
+// Mirrors src/index.js — enforce types / DX only.
+export function defineConfig(/** @type {any} */ options) {
+	return options;
+}
+
+/**
+ * The plugin factory must never run inside the built server: the sub-build
+ * aliases it away precisely because it drags the compiler + vite along.
+ * @returns {never}
+ */
+export function octane() {
+	throw new Error(
+		'[@octanejs/vite-plugin] octane() is a Vite plugin — it cannot run inside the production server bundle.',
+	);
+}

package/src/constants.js

@@ -1,2 +1,3 @@
+// @ts-check
 export const DEFAULT_OUTDIR = 'dist';
 export const ENTRY_FILENAME = 'entry.js';