@yak-io/nextjs 0.3.0 → 0.3.1

package/README.md

@@ -46,7 +46,7 @@ export default function RootLayout({ children }: { children: React.ReactNode })
 ### 2. Unified API route
 
 ```ts
-// app/api/yak/[...yak]/route.ts
+// app/api/yak/[[...yak]]/route.ts
 import { createNextYakHandler } from "@yak-io/nextjs/server";
 
 export const { GET, POST } = createNextYakHandler({
@@ -178,11 +178,13 @@ yak-nextjs generate-manifest --pages-dir ./src/pages
 yak-nextjs generate-manifest --app-dir ./app --output ./src/generated/routes.ts
 ```
 
-## Route Manifest for Production
+## Route Manifest for Production (Required)
 
-During local development, routes are scanned directly from the filesystem—no setup needed. However, when you build your Next.js app for production, only the compiled `.next` output is included. Source files like `./src/app` are not present at runtime.
+> **Important:** This setup is required for production deployments. Skip this only if you are providing your own custom routes via the `routes` or `getRoutes` options.
 
-### Recommended setup
+During local development, routes are scanned directly from the filesystem. However, when you build your Next.js app for production, only the compiled `.next` output is included—source files like `./src/app` are not present at runtime, causing route discovery to fail.
+
+### Required setup
 
 1. Add a `prebuild` script to generate the manifest before Next.js builds:
 
@@ -195,18 +197,49 @@ During local development, routes are scanned directly from the filesystem—no s
 }
 ```
 
-2. Use the route manifest adapter in your handler:
+The CLI auto-detects your directory structure. If your project uses non-standard paths, specify them explicitly:
+
+```json
+{
+  "scripts": {
+    "prebuild": "yak-nextjs generate-manifest --app-dir ./app --output ./app/yak.routes.ts",
+    "build": "next build"
+  }
+}
+```
+
+| Project structure | Command |
+|-------------------|-------------------------------------------------------|
+| `src/app/` (default) | `yak-nextjs generate-manifest` |
+| `app/` | `yak-nextjs generate-manifest --app-dir ./app --output ./app/yak.routes.ts` |
+| `src/app/` + `src/pages/` | `yak-nextjs generate-manifest --pages-dir ./src/pages` |
+| `app/` + `pages/` | `yak-nextjs generate-manifest --app-dir ./app --pages-dir ./pages --output ./app/yak.routes.ts` |
+
+2. Add the generated file to `.gitignore`:
+
+```gitignore
+# Generated route manifest (use the path matching your --output)
+src/yak.routes.ts
+# or for root app/ directory:
+# app/yak.routes.ts
+```
+
+3. Use the route manifest adapter in your handler:
 
 ```ts
-// app/api/yak/[...yak]/route.ts
+// app/api/yak/[[...yak]]/route.ts
 import { createNextYakHandler, createRouteManifestAdapter } from "@yak-io/nextjs/server";
-import { routes } from "@/yak.routes";
+import { routes } from "@/yak.routes"; // Adjust path based on your tsconfig paths
 
 export const { GET, POST } = createNextYakHandler({
   routes: createRouteManifestAdapter({ routes }),
 });
 ```
 
+> **Note:** The import path depends on your `tsconfig.json` paths. Common configurations:
+> - `src/yak.routes.ts` → `@/yak.routes` (when `@/*` maps to `./src/*`)
+> - `app/yak.routes.ts` → `@/yak.routes` (when `@/*` maps to `./app/*`) or `../../../yak.routes`
+
 The generated TypeScript module is imported directly, ensuring it's bundled with your serverless function automatically.
 
 ### Route filtering

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@yak-io/nextjs",
-  "version": "0.3.0",
+  "version": "0.3.1",
   "description": "Next.js SDK for embedding yak chatbot with route manifest generation",
   "type": "module",
   "license": "SEE LICENSE IN LICENSE",
@@ -60,8 +60,8 @@
     "yak-nextjs": "./dist/cli/generate-manifest.js"
   },
   "dependencies": {
-    "@yak-io/javascript": "0.3.0",
-    "@yak-io/react": "0.3.0"
+    "@yak-io/javascript": "0.4.0",
+    "@yak-io/react": "0.4.0"
   },
   "peerDependencies": {
     "next": "^14.0.0 || ^15.0.0 || ^16.0.0",
@@ -69,12 +69,12 @@
     "react-dom": "^18.0.0 || ^19.0.0"
   },
   "devDependencies": {
-    "@types/node": "^24.10.2",
-    "@types/react": "^19.2.7",
+    "@types/node": "^24.10.4",
+    "@types/react": "^19.2.10",
     "@types/react-dom": "^19.2.0",
-    "next": "^16.0.10",
-    "react": "^19.2.3",
-    "react-dom": "^19.2.3",
+    "next": "^16.1.6",
+    "react": "^19.2.4",
+    "react-dom": "^19.2.4",
     "typescript": "^5.3.0",
     "@repo/typescript-config": "0.0.0"
   },