@jaypie/mcp 0.7.3 → 0.7.4

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.3#f9c2b3fe"
+const BUILD_VERSION_STRING = "@jaypie/mcp@0.7.4#9b2629b2"
     ;
 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.3",
+  "version": "0.7.4",
   "description": "Jaypie MCP",
   "repository": {
     "type": "git",

package/release-notes/express/1.2.7.md

@@ -0,0 +1,48 @@
+---
+version: 1.2.7
+date: 2025-01-30
+summary: Fix CORS OPTIONS preflight hanging with Lambda streaming
+---
+
+## Bug Fix
+
+Fixed an issue where CORS OPTIONS preflight requests would hang indefinitely when using `createLambdaStreamHandler` with the `cors` middleware.
+
+### Problem
+
+When using Lambda response streaming, browser CORS preflight (OPTIONS) requests would hang because:
+- The standard cors package's call to `res.end()` could get delayed by streaming's async behavior
+- The Lambda response stream would stay open waiting for streaming data that never comes
+- Browsers would timeout waiting for the preflight response
+
+### Solution
+
+The `cors` middleware now detects OPTIONS requests early and handles them synchronously:
+- Sets all required CORS headers directly (Access-Control-Allow-Origin, Access-Control-Allow-Methods, etc.)
+- Terminates the response immediately with a 204 No Content status
+- Ensures the response stream doesn't enter streaming mode for preflight requests
+
+### Usage
+
+No changes required. The fix is automatic when using `cors` with `createLambdaStreamHandler`:
+
+```typescript
+import express from "express";
+import { cors, createLambdaStreamHandler } from "@jaypie/express";
+
+const app = express();
+app.use(cors({ origin: "https://example.com" }));
+
+// Streaming endpoint works correctly with CORS
+app.post("/stream", (req, res) => {
+  res.setHeader("Content-Type", "text/event-stream");
+  res.write("data: hello\n\n");
+  res.end();
+});
+
+export const handler = createLambdaStreamHandler(app);
+```
+
+### Related
+
+- GitHub Issue: [#174](https://github.com/finlaysonstudio/jaypie/issues/174)

package/skills/cors.md

@@ -317,6 +317,36 @@ app.use(cors({
 | `PROJECT_ENV` | Set to `sandbox` to enable localhost access |
 | `PROJECT_SANDBOX_MODE` | Set to `true` to enable localhost access |
 
+## Lambda Streaming Compatibility
+
+Jaypie's `cors` middleware is designed to work seamlessly with Lambda response streaming (`createLambdaStreamHandler`). Unlike the standard `cors` package, Jaypie's implementation handles OPTIONS preflight requests early and terminates them immediately, preventing the response stream from hanging.
+
+This is critical because:
+- Browser CORS preflight requests (OPTIONS) must complete quickly with a 204 response
+- Lambda streaming keeps the response stream open for streaming data
+- Without early termination, OPTIONS requests would hang waiting for streaming data that never comes
+
+No special configuration is needed—Jaypie's `cors` automatically detects OPTIONS requests and handles them appropriately.
+
+```typescript
+import express from "express";
+import { cors, createLambdaStreamHandler } from "@jaypie/express";
+
+const app = express();
+
+// CORS works automatically with streaming
+app.use(cors({ origin: "https://example.com" }));
+
+app.post("/stream", (req, res) => {
+  res.setHeader("Content-Type", "text/event-stream");
+  res.write("data: hello\n\n");
+  res.end();
+});
+
+// Deploy with Lambda streaming - CORS preflight works correctly
+export const handler = createLambdaStreamHandler(app);
+```
+
 ## See Also
 
 - **`skill("express")`** - Express handler and Lambda adapter documentation