@yak-io/nextjs 0.1.2 → 0.1.3

package/README.md

@@ -164,12 +164,12 @@ Behind the scenes `@yak-io/javascript` merges every `RouteSource` into a single
 yak-nextjs generate-manifest
 ```
 
-Use the CLI when you prefer to pre-compute a manifest at build time. The JSON matches the runtime manifest structure exposed by the handlers.
+Use the CLI to pre-compute a manifest at build time. The JSON matches the runtime manifest structure exposed by the handlers.
 
 **Options:**
 - `--app-dir <path>` – Path to Next.js app directory (default: `./src/app`)
 - `--pages-dir <path>` – Path to Next.js pages directory (optional, scanned in addition to app-dir)
-- `--output <path>` – Output file path (default: `./yak-routes-manifest.json`)
+- `--output <path>` – Output file path (default: `./public/yak-routes-manifest.json`)
 
 **Examples:**
 ```bash
@@ -197,22 +197,9 @@ Add a `prebuild` script to generate the manifest before Next.js builds:
 }
 ```
 
-This uses the defaults (`./src/app` → `./yak-routes-manifest.json`). Customize if needed:
+That's it! The manifest is generated to `./public/yak-routes-manifest.json` and the handler automatically fetches it at runtime on serverless platforms like Vercel. No code changes needed.
 
-```json
-{
-  "scripts": {
-    "prebuild": "yak-nextjs generate-manifest --app-dir ./app --output ./routes.json"
-  }
-}
-```
-
-> **Important:** The manifest must be in the project root (not `public/`). On Vercel and other serverless platforms, files in `public/` are served via CDN and are not available on the function's filesystem.
-
-The handler checks these locations automatically:
-1. `./yak-routes-manifest.json`
-2. `./.next/yak-routes-manifest.json`
-3. `./public/yak-routes-manifest.json` (only works in non-serverless environments)
+The handler automatically detects the deployment environment (Vercel via `VERCEL_URL`, Netlify via `URL`, or custom `NEXT_PUBLIC_BASE_URL`) and fetches the manifest from the public folder.
 
 ### Alternative: explicit routes
 
@@ -227,24 +214,14 @@ export const { GET, POST } = createNextYakHandler({
 });
 ```
 
-### Loading a custom manifest location
-
-```ts
-import { createNextYakHandler, loadRoutes } from "@yak-io/nextjs/server";
-
-export const { GET, POST } = createNextYakHandler({
-  routes: loadRoutes("./custom/manifest.json"),
-});
-```
-
 ## API surface (server)
 
 `@yak-io/nextjs/server` exports:
 
 - `scanRoutes(directory: string, options?: { directoryType?: "app" | "pages" })` – low-level filesystem scanner (useful for precomputing manifests or composing custom sources). Only captures page routes, extracting `title` and `description` from static metadata exports.
-- `loadRouteManifest(path?: string)` – load a pre-built JSON manifest, returns `null` if not found. Checks `./yak-routes-manifest.json`, `./.next/yak-routes-manifest.json`, and `./public/yak-routes-manifest.json` by default.
+- `loadRouteManifest(path?: string)` – load a pre-built JSON manifest via filesystem read, returns `null` if not found.
 - `loadRoutes(path?: string)` – load routes from a manifest, throws with helpful error if not found.
-- `createNextYakHandler(config)` – unified GET + POST handler (wrapping `createYakHandler`). When `routes`/`getRoutes` are omitted it auto-scans `./src/app` and `./src/pages` (override with `appDir`/`pagesDir`, and narrow results via `routeFilter?: { include?: RegExp[]; exclude?: RegExp[] }`). In production, automatically falls back to pre-built manifests.
+- `createNextYakHandler(config)` – unified GET + POST handler. When `routes`/`getRoutes` are omitted it auto-scans `./src/app` (override with `appDir`). In production, automatically fetches manifest from public folder.
 - `createNextYakConfigHandler(config)` – GET-only convenience wrapper.
 - `createNextYakToolsHandler(config)` – POST-only wrapper.
 - Re-exported types from `@yak-io/javascript/server` (RouteInfo, RouteManifest, ToolDefinition, ToolManifest, ToolExecutor, ChatConfig, RouteSourceInput, ToolSourceInput, etc.).

package/dist/cli/generate-manifest.d.ts

@@ -11,7 +11,7 @@
  * Options:
  *   --app-dir <path>     Path to Next.js app directory (default: ./src/app)
  *   --pages-dir <path>   Path to Next.js pages directory (optional, scanned in addition to app-dir)
- *   --output <path>      Output file path (default: ./yak-routes-manifest.json)
+ *   --output <path>      Output file path (default: ./public/yak-routes-manifest.json)
  */
 export {};
 //# sourceMappingURL=generate-manifest.d.ts.map

package/dist/cli/generate-manifest.js

@@ -11,7 +11,7 @@
  * Options:
  *   --app-dir <path>     Path to Next.js app directory (default: ./src/app)
  *   --pages-dir <path>   Path to Next.js pages directory (optional, scanned in addition to app-dir)
- *   --output <path>      Output file path (default: ./yak-routes-manifest.json)
+ *   --output <path>      Output file path (default: ./public/yak-routes-manifest.json)
  */
 import * as fs from "node:fs";
 import * as path from "node:path";
@@ -201,7 +201,7 @@ function parseArgs() {
     const args = process.argv.slice(2);
     let appDir = "./src/app";
     let pagesDir = undefined;
-    let output = "./yak-routes-manifest.json";
+    let output = "./public/yak-routes-manifest.json";
     let help = false;
     for (let i = 0; i < args.length; i++) {
         const arg = args[i];
@@ -238,7 +238,7 @@ Usage:
 Options:
   --app-dir <path>     Path to Next.js app directory (default: ./src/app)
   --pages-dir <path>   Path to Next.js pages directory (optional)
-  --output <path>      Output file path (default: ./yak-routes-manifest.json)
+  --output <path>      Output file path (default: ./public/yak-routes-manifest.json)
   --help, -h           Show this help message
 
 Examples:
@@ -290,6 +290,7 @@ function main() {
         generated_at: new Date().toISOString(),
     };
     const outputPath = path.resolve(process.cwd(), output);
+    // Write JSON manifest
     fs.writeFileSync(outputPath, JSON.stringify(manifest, null, 2), "utf-8");
     console.log(`✅ Generated manifest with ${uniqueRoutes.length} page routes`);
     console.log(`   Output: ${outputPath}`);

package/dist/server/createNextYakHandler.d.ts

@@ -1,9 +1,8 @@
 import type { RouteSourceInput, ToolSourceInput, RouteInfo, RouteManifest, ToolManifest, ToolExecutor } from "@yak-io/javascript/server";
 /**
- * Load a pre-built route manifest from disk.
+ * Load a pre-built route manifest from disk (JSON file).
  *
- * This should be used in production environments where filesystem scanning
- * is not available (e.g., Vercel serverless functions).
+ * This works in traditional Node.js deployments where the filesystem is available.
  *
  * Generate the manifest at build time using:
  *   yak-nextjs generate-manifest

package/dist/server/createNextYakHandler.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"createNextYakHandler.d.ts","sourceRoot":"","sources":["../../src/server/createNextYakHandler.ts"],"names":[],"mappings":"AAOA,OAAO,KAAK,EACV,gBAAgB,EAChB,eAAe,EACf,SAAS,EACT,aAAa,EACb,YAAY,EACZ,YAAY,EACb,MAAM,2BAA2B,CAAC;AAgBnC;;;;;;;;;;;GAWG;AACH,wBAAgB,iBAAiB,CAAC,YAAY,CAAC,EAAE,MAAM,GAAG,aAAa,GAAG,IAAI,CAgB7E;AAED;;;GAGG;AACH,wBAAgB,UAAU,CAAC,YAAY,CAAC,EAAE,MAAM,GAAG,SAAS,EAAE,CAa7D;AAED,MAAM,MAAM,kBAAkB,GAAG;IAC/B,OAAO,CAAC,EAAE,MAAM,EAAE,CAAC;IACnB,OAAO,CAAC,EAAE,MAAM,EAAE,CAAC;CACpB,CAAC;AAEF,MAAM,MAAM,oBAAoB,GAAG;IACjC,MAAM,CAAC,EAAE,MAAM,CAAC;IAChB,WAAW,CAAC,EAAE,kBAAkB,CAAC;IACjC,MAAM,CAAC,EAAE,gBAAgB,CAAC;IAC1B,SAAS,CAAC,EAAE,MAAM,OAAO,CAAC,SAAS,EAAE,CAAC,CAAC;IACvC,KAAK,CAAC,EAAE,eAAe,CAAC;IACxB,QAAQ,CAAC,EAAE,MAAM,GAAG,KAAK,CAAC;IAC1B,QAAQ,CAAC,EAAE,MAAM,OAAO,CAAC,YAAY,CAAC,CAAC;IACvC,WAAW,CAAC,EAAE,YAAY,CAAC;CAC5B,CAAC;AAEF;;GAEG;AACH,wBAAgB,oBAAoB,CAAC,MAAM,EAAE,oBAAoB;;;EAKhE;AA6FD,MAAM,MAAM,0BAA0B,GAAG;IACvC,MAAM,CAAC,EAAE,MAAM,CAAC;IAChB,WAAW,CAAC,EAAE,kBAAkB,CAAC;IACjC,MAAM,CAAC,EAAE,gBAAgB,CAAC;IAC1B,SAAS,CAAC,EAAE,MAAM,OAAO,CAAC,SAAS,EAAE,CAAC,CAAC;IACvC,KAAK,CAAC,EAAE,eAAe,CAAC;IACxB,QAAQ,CAAC,EAAE,MAAM,OAAO,CAAC,YAAY,CAAC,CAAC;CACxC,CAAC;AAEF,wBAAgB,0BAA0B,CAAC,MAAM,EAAE,0BAA0B,wCAK5E;AAED,MAAM,MAAM,yBAAyB,GAAG;IACtC,KAAK,CAAC,EAAE,eAAe,CAAC;IACxB,QAAQ,CAAC,EAAE,MAAM,OAAO,CAAC,YAAY,CAAC,CAAC;IACvC,WAAW,EAAE,YAAY,CAAC;CAC3B,CAAC;AAEF,wBAAgB,yBAAyB,CAAC,MAAM,EAAE,yBAAyB,uCAW1E"}
+{"version":3,"file":"createNextYakHandler.d.ts","sourceRoot":"","sources":["../../src/server/createNextYakHandler.ts"],"names":[],"mappings":"AAOA,OAAO,KAAK,EACV,gBAAgB,EAChB,eAAe,EACf,SAAS,EACT,aAAa,EACb,YAAY,EACZ,YAAY,EACb,MAAM,2BAA2B,CAAC;AAiBnC;;;;;;;;;;GAUG;AACH,wBAAgB,iBAAiB,CAAC,YAAY,CAAC,EAAE,MAAM,GAAG,aAAa,GAAG,IAAI,CAgB7E;AAgED;;;GAGG;AACH,wBAAgB,UAAU,CAAC,YAAY,CAAC,EAAE,MAAM,GAAG,SAAS,EAAE,CAe7D;AAED,MAAM,MAAM,kBAAkB,GAAG;IAC/B,OAAO,CAAC,EAAE,MAAM,EAAE,CAAC;IACnB,OAAO,CAAC,EAAE,MAAM,EAAE,CAAC;CACpB,CAAC;AAEF,MAAM,MAAM,oBAAoB,GAAG;IACjC,MAAM,CAAC,EAAE,MAAM,CAAC;IAChB,WAAW,CAAC,EAAE,kBAAkB,CAAC;IACjC,MAAM,CAAC,EAAE,gBAAgB,CAAC;IAC1B,SAAS,CAAC,EAAE,MAAM,OAAO,CAAC,SAAS,EAAE,CAAC,CAAC;IACvC,KAAK,CAAC,EAAE,eAAe,CAAC;IACxB,QAAQ,CAAC,EAAE,MAAM,GAAG,KAAK,CAAC;IAC1B,QAAQ,CAAC,EAAE,MAAM,OAAO,CAAC,YAAY,CAAC,CAAC;IACvC,WAAW,CAAC,EAAE,YAAY,CAAC;CAC5B,CAAC;AAEF;;GAEG;AACH,wBAAgB,oBAAoB,CAAC,MAAM,EAAE,oBAAoB;;;EAKhE;AAmGD,MAAM,MAAM,0BAA0B,GAAG;IACvC,MAAM,CAAC,EAAE,MAAM,CAAC;IAChB,WAAW,CAAC,EAAE,kBAAkB,CAAC;IACjC,MAAM,CAAC,EAAE,gBAAgB,CAAC;IAC1B,SAAS,CAAC,EAAE,MAAM,OAAO,CAAC,SAAS,EAAE,CAAC,CAAC;IACvC,KAAK,CAAC,EAAE,eAAe,CAAC;IACxB,QAAQ,CAAC,EAAE,MAAM,OAAO,CAAC,YAAY,CAAC,CAAC;CACxC,CAAC;AAEF,wBAAgB,0BAA0B,CAAC,MAAM,EAAE,0BAA0B,wCAK5E;AAED,MAAM,MAAM,yBAAyB,GAAG;IACtC,KAAK,CAAC,EAAE,eAAe,CAAC;IACxB,QAAQ,CAAC,EAAE,MAAM,OAAO,CAAC,YAAY,CAAC,CAAC;IACvC,WAAW,EAAE,YAAY,CAAC;CAC3B,CAAC;AAEF,wBAAgB,yBAAyB,CAAC,MAAM,EAAE,yBAAyB,uCAW1E"}

package/dist/server/createNextYakHandler.js

@@ -3,22 +3,21 @@ import * as fs from "node:fs";
 import * as path from "node:path";
 import { scanRoutes } from "./scan-routes.js";
 /**
- * Default paths to check for pre-built route manifests.
- *
- * On Vercel/serverless, files in `public/` are served via CDN and NOT available
- * on the function's filesystem. The manifest must be in the project root or
- * another location that gets bundled with the serverless function.
+ * Default paths to check for pre-built route manifests (JSON files).
+ * These are read via fs.readFileSync at runtime.
  */
 const DEFAULT_MANIFEST_PATHS = [
+    "./public/yak-routes-manifest.json",
     "./yak-routes-manifest.json",
-    "./.next/yak-routes-manifest.json",
-    "./public/yak-routes-manifest.json", // Only works in non-serverless environments
 ];
 /**
- * Load a pre-built route manifest from disk.
+ * Public URL path where the manifest is served from (when in public/).
+ */
+const PUBLIC_MANIFEST_URL = "/yak-routes-manifest.json";
+/**
+ * Load a pre-built route manifest from disk (JSON file).
  *
- * This should be used in production environments where filesystem scanning
- * is not available (e.g., Vercel serverless functions).
+ * This works in traditional Node.js deployments where the filesystem is available.
  *
  * Generate the manifest at build time using:
  *   yak-nextjs generate-manifest
@@ -42,6 +41,59 @@ export function loadRouteManifest(manifestPath) {
     }
     return null;
 }
+/**
+ * Fetch the route manifest from the public URL.
+ * Used in serverless environments where filesystem access is not available.
+ */
+async function fetchRouteManifest() {
+    // Try to determine the base URL for fetching
+    const baseUrl = getBaseUrl();
+    if (!baseUrl) {
+        return null;
+    }
+    try {
+        const url = new URL(PUBLIC_MANIFEST_URL, baseUrl);
+        const response = await fetch(url.toString(), {
+            headers: { "Accept": "application/json" },
+            cache: "no-store",
+        });
+        if (!response.ok) {
+            return null;
+        }
+        const manifest = await response.json();
+        if (manifest?.routes) {
+            return manifest;
+        }
+    }
+    catch {
+        // Fetch failed
+    }
+    return null;
+}
+/**
+ * Get the base URL for the current deployment.
+ * Supports Vercel, Netlify, and custom configurations.
+ */
+function getBaseUrl() {
+    // Vercel provides VERCEL_URL (without protocol)
+    if (process.env.VERCEL_URL) {
+        const protocol = process.env.VERCEL_ENV === "development" ? "http" : "https";
+        return `${protocol}://${process.env.VERCEL_URL}`;
+    }
+    // Netlify provides URL
+    if (process.env.URL) {
+        return process.env.URL;
+    }
+    // Custom base URL
+    if (process.env.NEXT_PUBLIC_BASE_URL) {
+        return process.env.NEXT_PUBLIC_BASE_URL;
+    }
+    // For local development
+    if (process.env.NODE_ENV === "development") {
+        return "http://localhost:3000";
+    }
+    return null;
+}
 /**
  * Load routes from a pre-built manifest.
  * Throws if manifest is not found.
@@ -49,7 +101,9 @@ export function loadRouteManifest(manifestPath) {
 export function loadRoutes(manifestPath) {
     const manifest = loadRouteManifest(manifestPath);
     if (!manifest) {
-        const pathsChecked = manifestPath ? manifestPath : DEFAULT_MANIFEST_PATHS.join(", ");
+        const pathsChecked = manifestPath
+            ? manifestPath
+            : [...DEFAULT_MANIFEST_PATHS].join(", ");
         throw new Error(`Route manifest not found. Checked: ${pathsChecked}\n\n` +
             `In production environments (like Vercel), route scanning requires a pre-built manifest.\n` +
             `Generate it at build time by adding to your build script:\n\n` +
@@ -68,30 +122,36 @@ export function createNextYakHandler(config) {
     });
 }
 /**
- * Attempt to scan routes from filesystem, with production-safe fallback.
+ * Attempt to load routes from filesystem or fetch from public URL.
  *
  * In development: scans the app directory directly
- * In production (Vercel, etc.): falls back to pre-built manifest if directory doesn't exist
+ * In production (Vercel, etc.): falls back to pre-built manifest via filesystem or HTTP fetch
  */
-function tryLoadRoutes(appDir) {
+async function tryLoadRoutes(appDir) {
     const targetDir = path.resolve(process.cwd(), appDir);
     // If the app directory exists, scan it directly (development mode)
     if (fs.existsSync(targetDir)) {
         return scanRoutes(appDir);
     }
-    // In production, the source directory doesn't exist - try loading from manifest
+    // In production, the source directory doesn't exist - try loading from manifest file
     const manifest = loadRouteManifest();
     if (manifest) {
         return manifest.routes;
     }
+    // Try fetching from public URL (works on Vercel/serverless)
+    const fetchedManifest = await fetchRouteManifest();
+    if (fetchedManifest) {
+        return fetchedManifest.routes;
+    }
     // Neither source nor manifest available - provide helpful error
     throw new Error(`App directory not found: ${targetDir}\n\n` +
         `This typically happens in production (Vercel, etc.) where source files aren't deployed.\n\n` +
         `Solutions:\n` +
-        `1. Generate a route manifest at build time:\n` +
-        `   Add to your build script: yak-nextjs generate-manifest\n\n` +
+        `1. Generate a route manifest at build time (recommended):\n` +
+        `   Add to package.json: "prebuild": "yak-nextjs generate-manifest"\n` +
+        `   The manifest will be placed in public/ and automatically loaded.\n\n` +
         `2. Provide routes explicitly:\n` +
-        `   createNextYakHandler({ routes: [...] })\n\n` +
+        `   createNextYakHandler({ routes: [{ path: "/", title: "Home" }, ...] })\n\n` +
         `3. Use getRoutes callback:\n` +
         `   createNextYakHandler({ getRoutes: async () => [...] })`);
 }
@@ -102,7 +162,10 @@ function resolveRouteSources(config) {
     if (config.getRoutes) {
         return config.getRoutes;
     }
-    return async () => applyRouteFilters(tryLoadRoutes(config.appDir ?? "./src/app"), config.routeFilter);
+    return async () => {
+        const routes = await tryLoadRoutes(config.appDir ?? "./src/app");
+        return applyRouteFilters(routes, config.routeFilter);
+    };
 }
 function applyRouteFilters(routes, filter) {
     if (!filter) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@yak-io/nextjs",
-  "version": "0.1.2",
+  "version": "0.1.3",
   "description": "Next.js SDK for embedding yak chatbot with route manifest generation",
   "type": "module",
   "license": "SEE LICENSE IN LICENSE",