@go-to-k/cdkd 0.119.0 → 0.121.0

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.
Files changed (9) hide show
  1. package/README.md +4 -2
  2. package/dist/cli.js +520 -27
  3. package/dist/cli.js.map +1 -1
  4. package/dist/{deploy-engine-Chzg_hDE.js → deploy-engine-B2RZT3ai.js} +46 -11
  5. package/dist/deploy-engine-B2RZT3ai.js.map +1 -0
  6. package/dist/index.d.ts.map +1 -1
  7. package/dist/index.js +1 -1
  8. package/package.json +1 -1
  9. package/dist/deploy-engine-Chzg_hDE.js.map +0 -1
package/README.md CHANGED
@@ -6,7 +6,7 @@ Drop-in CDK CLI for existing CDK apps — faster deploys via AWS SDK instead of
6
6
  - **Up to 15x faster deploys than the AWS CDK CLI (CloudFormation)**
7
7
  - **Local dev for CDK apps** — invoke Lambdas, serve API Gateway routes, and run ECS tasks directly from your CDK code, no `cdk synth → sam local` round-trip.
8
8
 
9
- ![cdkd demo](https://github.com/user-attachments/assets/0128730d-186d-4bd3-abea-aabc80ba4dd5)
9
+ ![cdk deploy vs cdkd deploy — side-by-side, 35s recording, real AWS deploy. cdkd finishes while cdk is still creating its CloudFormation changeset.](assets/cdk-vs-cdkd.gif)
10
10
 
11
11
  **cdkd complements the AWS CDK CLI rather than replacing it.** Use cdkd in dev/test for rapid iteration and SAM-style local execution; use the AWS CDK CLI in production for full CloudFormation tooling. Bidirectional migration is supported — [import an existing CloudFormation stack](#importing-existing-resources) into cdkd for iteration, or [export back to CloudFormation](#exporting-a-stack-back-to-cloudformation) when ready for production.
12
12
 
@@ -457,7 +457,9 @@ cdkd local start-api --from-state # substitute deployed env vars
457
457
  One server per discovered API — authorizers, CORS configs, and stage
458
458
  variables stay scoped to the owning API. Supports REST v1 + HTTP API +
459
459
  Function URL with AWS_PROXY integrations; Lambda TOKEN / REQUEST,
460
- Cognito User Pool, and HTTP v2 JWT authorizers (JWKS-verified); CORS
460
+ Cognito User Pool, HTTP v2 JWT authorizers (JWKS-verified), and REST v1
461
+ `AuthorizationType: 'AWS_IAM'` (SigV4 signature verification only — IAM
462
+ policy evaluation is not emulated; see `docs/local-emulation.md`); CORS
461
463
  preflight (HTTP API v2 `CorsConfiguration` + REST v1 OPTIONS MOCK
462
464
  preflight from `defaultCorsPreflightOptions`); hot reload via `--watch`;
463
465
  deploy-state-backed env var substitution via `--from-state`.