@jaypie/mcp 0.7.13 → 0.7.15
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -9,7 +9,7 @@ import { gt } from 'semver';
|
|
|
9
9
|
/**
|
|
10
10
|
* Docs Suite - Documentation services (skill, version, release_notes)
|
|
11
11
|
*/
|
|
12
|
-
const BUILD_VERSION_STRING = "@jaypie/mcp@0.7.
|
|
12
|
+
const BUILD_VERSION_STRING = "@jaypie/mcp@0.7.15#2d2a7db9"
|
|
13
13
|
;
|
|
14
14
|
const __filename$1 = fileURLToPath(import.meta.url);
|
|
15
15
|
const __dirname$1 = path.dirname(__filename$1);
|
package/package.json
CHANGED
|
@@ -0,0 +1,21 @@
|
|
|
1
|
+
---
|
|
2
|
+
version: 1.2.12
|
|
3
|
+
date: 2026-02-05
|
|
4
|
+
summary: Fix non-streaming expressHandler endpoints hanging in Lambda streaming mode
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
## Fixes
|
|
8
|
+
|
|
9
|
+
- **Lambda Streaming**: Fixed `expressHandler` endpoints that return data (non-streaming) hanging when used with `createLambdaStreamHandler`. The issue was that `safeSendJson()` called `flushHeaders()` before setting `content-type`, causing the JSON response to never be properly delivered to Lambda's response stream.
|
|
10
|
+
|
|
11
|
+
## Technical Details
|
|
12
|
+
|
|
13
|
+
The fix ensures proper order of operations for Lambda streaming responses:
|
|
14
|
+
1. Set status code
|
|
15
|
+
2. Set `content-type: application/json` header
|
|
16
|
+
3. Flush headers to initialize the Lambda stream wrapper
|
|
17
|
+
4. Write JSON data directly via `res.end()` instead of `res.json()`
|
|
18
|
+
|
|
19
|
+
This allows applications to use both streaming (SSE) and non-streaming (REST API) endpoints in the same Express app with `createLambdaStreamHandler`.
|
|
20
|
+
|
|
21
|
+
Fixes #187
|
|
@@ -0,0 +1,19 @@
|
|
|
1
|
+
---
|
|
2
|
+
version: 1.2.13
|
|
3
|
+
date: 2026-02-05
|
|
4
|
+
summary: Fix request stream not ending for GET requests without body in Lambda streaming mode
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
## Fixes
|
|
8
|
+
|
|
9
|
+
- **Lambda Streaming**: Fixed GET requests without a body hanging when using `createLambdaStreamHandler` with `expressHandler`. The issue was that the request stream never emitted 'end' for bodyless requests, causing middleware (like `express.json()`) that waits for the stream to hang forever.
|
|
10
|
+
|
|
11
|
+
## Technical Details
|
|
12
|
+
|
|
13
|
+
The `LambdaRequest` class now always schedules a `process.nextTick` to push `null` to the stream (signaling end), even for requests without a body. Previously, this was only done for requests WITH a body, leaving GET requests in a perpetual "waiting" state.
|
|
14
|
+
|
|
15
|
+
This fix complements the 1.2.12 fix - together they fully resolve issue #187:
|
|
16
|
+
- **1.2.12**: Fixed `safeSendJson` setting content-type before flushing headers
|
|
17
|
+
- **1.2.13**: Fixed request stream never ending for bodyless requests
|
|
18
|
+
|
|
19
|
+
Fixes #187
|