@jaypie/mcp 0.7.1 → 0.7.2

package/dist/suites/docs/index.js

@@ -9,7 +9,7 @@ import { gt } from 'semver';
 /**
  * Docs Suite - Documentation services (skill, version, release_notes)
  */
-const BUILD_VERSION_STRING = "@jaypie/mcp@0.7.1#82d19d8a"
+const BUILD_VERSION_STRING = "@jaypie/mcp@0.7.2#5d947297"
     ;
 const __filename$1 = fileURLToPath(import.meta.url);
 const __dirname$1 = path.dirname(__filename$1);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jaypie/mcp",
-  "version": "0.7.1",
+  "version": "0.7.2",
   "description": "Jaypie MCP",
   "repository": {
     "type": "git",

package/release-notes/mcp/0.7.2.md

@@ -0,0 +1,18 @@
+---
+version: 0.7.2
+date: 2026-01-30
+summary: Document JaypieNextJs streaming configuration requirements
+---
+
+## Documentation
+
+- Added JaypieNextJs streaming documentation to `streaming.md` skill
+- Added JaypieNextJs construct to `cdk.md` skill
+- Clarified that `streaming: true` requires `open-next.config.ts` with `aws-lambda-streaming` wrapper
+
+## Context
+
+Issue #171 reported that `JaypieNextJs` with `streaming: true` returns a JSON envelope instead of streamed HTML. This is expected behavior - Lambda response streaming requires both:
+
+1. CDK: `streaming: true` (configures `InvokeMode: RESPONSE_STREAM`)
+2. Next.js: `open-next.config.ts` with `wrapper: "aws-lambda-streaming"`

package/skills/cdk.md

@@ -139,7 +139,24 @@ const handler = new JaypieLambda(this, "Handler", {
 });
 ```
 
+## JaypieNextJs
+
+Deploy Next.js applications:
+
+```typescript
+import { JaypieNextJs } from "@jaypie/constructs";
+
+new JaypieNextJs(this, "App", {
+  nextjsPath: "../nextjs",
+  domainName: "app.example.com",
+  hostedZone: "example.com",
+  streaming: true,  // Optional: enables response streaming
+});
+```
+
+**Streaming Note:** When `streaming: true`, also create `open-next.config.ts` in your Next.js app with `wrapper: "aws-lambda-streaming"`. See `skill("streaming")` for details.
+
 ## See Also
 
-- **`skill("streaming")`** - JaypieDistribution with `streaming: true` for response streaming
+- **`skill("streaming")`** - JaypieDistribution and JaypieNextJs streaming configuration
 - **`skill("websockets")`** - JaypieWebSocket and JaypieWebSocketTable constructs

package/skills/streaming.md

@@ -76,6 +76,8 @@ export const handler = lambdaStreamHandler(async (event, context) => {
 
 ## CDK Configuration
 
+### JaypieDistribution
+
 ```typescript
 import { JaypieLambda, JaypieDistribution } from "@jaypie/constructs";
 
@@ -90,6 +92,40 @@ new JaypieDistribution(this, "Api", {
 });
 ```
 
+### JaypieNextJs Streaming
+
+For Next.js applications with `JaypieNextJs`, streaming requires **two** configurations:
+
+1. **CDK** - Set `streaming: true` in the construct
+2. **Next.js App** - Create `open-next.config.ts` with the streaming wrapper
+
+```typescript
+// CDK Stack
+import { JaypieNextJs } from "@jaypie/constructs";
+
+new JaypieNextJs(this, "App", {
+  nextjsPath: "../nextjs",
+  streaming: true,
+});
+```
+
+```typescript
+// nextjs/open-next.config.ts (required for streaming)
+import type { OpenNextConfig } from "@opennextjs/aws/types/open-next.js";
+
+const config = {
+  default: {
+    override: {
+      wrapper: "aws-lambda-streaming",
+    },
+  },
+} satisfies OpenNextConfig;
+
+export default config;
+```
+
+**Important:** Without `open-next.config.ts`, the Lambda returns a JSON envelope `{ statusCode, headers, body }` instead of streaming HTML. This is because `cdk-nextjs-standalone` configures the Lambda Function URL with `RESPONSE_STREAM` invoke mode, but OpenNext also needs to be configured to use the streaming wrapper.
+
 ## Error Handling
 
 Errors are written to the stream in the configured format: