@jaypie/mcp 0.7.11 → 0.7.13

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.11#d7ce271c"
+const BUILD_VERSION_STRING = "@jaypie/mcp@0.7.13#96cbf210"
     ;
 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.11",
+  "version": "0.7.13",
   "description": "Jaypie MCP",
   "repository": {
     "type": "git",

package/release-notes/constructs/1.2.29.md

@@ -0,0 +1,15 @@
+---
+version: 1.2.29
+date: 2026-02-04
+summary: CloudFront invalidation permission and SSM access for SSO
+---
+
+# @jaypie/constructs 1.2.29
+
+## Bug Fixes
+
+- **JaypieWebDeploymentBucket**: Deploy role now includes `cloudfront:CreateInvalidation` permission when a CloudFront distribution is created, enabling GitHub Actions workflows to invalidate cache after deploying content
+
+## Features
+
+- **JaypieSsoPermissions**: Added `ssm:*` to developer permission set for Systems Manager access

package/release-notes/express/1.2.11.md

@@ -0,0 +1,14 @@
+---
+version: 1.2.11
+date: 2025-02-03
+summary: Fix Lambda streaming for 204 No Content responses and remove deprecated CDK feature flag
+---
+
+## Fixes
+
+- **Lambda Streaming**: Fixed 204 No Content responses not being properly handled in streaming mode
+- **CDK Compatibility**: Removed deprecated CDKv1 `grantWriteWithoutAcl` feature flag
+
+## Internal
+
+- Diagnostic headers added during debugging have been removed

package/release-notes/jaypie/1.2.9.md

@@ -0,0 +1,9 @@
+---
+version: 1.2.9
+date: 2025-02-03
+summary: Update to @jaypie/express 1.2.11 with Lambda streaming fixes
+---
+
+## Dependencies
+
+- Updated `@jaypie/express` to ^1.2.11

package/release-notes/mcp/0.7.12.md

@@ -0,0 +1,15 @@
+---
+version: 0.7.12
+date: 2025-02-03
+summary: Add ESM Lambda deployment documentation to express, lambda, and cdk skills
+---
+
+## Documentation
+
+- **express skill**: Added "Lambda ESM Bundling" section with full esbuild config for `.mjs` output
+- **lambda skill**: Added "ESM Deployment" section explaining `.mjs` vs `package.json` approaches
+- **cdk skill**: Added "Pre-built Code" section for JaypieLambda with `code` prop
+
+## Key Pattern
+
+Use `.mjs` extension for ESM Lambda bundles - Node.js always treats `.mjs` as ESM regardless of `package.json`.

package/skills/cdk.md

@@ -34,6 +34,19 @@ const handler = new JaypieLambda(this, "ApiHandler", {
 });
 ```
 
+#### Pre-built Code
+
+When using `code` instead of `entry` for pre-built bundles:
+
+```typescript
+new JaypieLambda(this, "Api", {
+  code: "../api/dist",     // Pre-built bundle directory
+  handler: "index.handler", // Lambda finds index.mjs automatically
+});
+```
+
+For ESM bundles, use `.mjs` extension or include `package.json` with `"type": "module"` in dist. See `skill("express")` for full esbuild config.
+
 ### JaypieQueue
 
 SQS queue with DLQ and Lambda trigger:

package/skills/express.md

@@ -153,6 +153,71 @@ new JaypieLambda(this, "Api", {
 
 The package includes Docker/SAM CLI setups for local testing in `packages/express/docker/`. See that directory's documentation for details.
 
+## Lambda ESM Bundling
+
+When deploying Express to Lambda with ESM, use esbuild with `.mjs` output.
+
+### Config File Approach
+
+Create `esbuild.config.mjs`:
+
+```javascript
+import { build } from "esbuild";
+import { builtinModules } from "module";
+
+await build({
+  entryPoints: ["index.ts"],
+  bundle: true,
+  minify: true,
+  platform: "node",
+  target: "node24",
+  format: "esm",
+  outfile: "dist/index.mjs",
+  external: [
+    "@aws-sdk/*",
+    ...builtinModules,
+    ...builtinModules.map(m => `node:${m}`),
+  ],
+  banner: {
+    js: `import { createRequire } from "module";
+import { fileURLToPath } from "url";
+import { dirname } from "path";
+const require = createRequire(import.meta.url);
+const __filename = fileURLToPath(import.meta.url);
+const __dirname = dirname(__filename);`,
+  },
+});
+```
+
+Add to package.json:
+
+```json
+{
+  "scripts": {
+    "build": "node esbuild.config.mjs"
+  }
+}
+```
+
+### Why .mjs?
+
+Node.js always treats `.mjs` files as ESM, regardless of `package.json`. No need to emit extra files.
+
+### Why createRequire banner?
+
+Some dependencies use `require()` even when bundled. The banner provides CommonJS shims for `require`, `__filename`, and `__dirname`.
+
+### CDK Integration
+
+Reference the `.mjs` file in your CDK stack:
+
+```typescript
+new JaypieLambda(this, "Api", {
+  code: "../api/dist",     // Pre-built bundle
+  handler: "index.handler", // Lambda finds index.mjs automatically
+});
+```
+
 ## See Also
 
 - **`skill("streaming")`** - Full guide to `expressStreamHandler` and `createLambdaStreamHandler`

package/skills/lambda.md

@@ -158,6 +158,36 @@ new JaypieLambda(this, "Handler", {
 });
 ```
 
+## ESM Deployment
+
+Lambda handlers using ESM require Node.js to recognize the module format.
+
+### Recommended: Use .mjs extension
+
+Files with `.mjs` extension are always treated as ESM by Node.js. Bundle with esbuild:
+
+```javascript
+await build({
+  format: "esm",
+  outfile: "dist/index.mjs",
+  // ...
+});
+```
+
+See `skill("express")` for the full esbuild config including the createRequire banner.
+
+### Alternative: Emit package.json
+
+If using `.js` extension, include `{"type":"module"}` in the dist folder.
+
+### Why This Matters
+
+Without the ESM signal, Lambda fails with:
+
+```
+Runtime.UserCodeSyntaxError: SyntaxError: Cannot use import statement outside a module
+```
+
 ## See Also
 
 - **`skill("streaming")`** - Full guide to `lambdaStreamHandler`, formats, and streaming utilities