Superseded. The Lambda adapter now ships inside
dynamodb-toolkitas thedynamodb-toolkit/lambdasubpath export (3.8.0+). This package is a frozen re-export thunk: it keeps existing consumers working unchanged and receives no further development. The repository is archived.
Change the imports — nothing else:
-import {createLambdaAdapter} from 'dynamodb-toolkit-lambda';
+import {createLambdaAdapter} from 'dynamodb-toolkit/lambda';
-import {createNodeListener, createFetchBridge} from 'dynamodb-toolkit-lambda/local.js';
+import {createNodeListener, createFetchBridge} from 'dynamodb-toolkit/lambda/local.js';Then drop dynamodb-toolkit-lambda from your package.json. The API, options, event-shape auto-detection (API Gateway v1 / v2, Function URL, ALB), and wire contract are identical — the code simply lives in the core package now.
export * from 'dynamodb-toolkit/lambda' (plus path-compat re-exports for local.js and read-lambda-body.js) — nothing else. It declares an open-ended peer on dynamodb-toolkit >= 3.8.0, so future core releases never require a thunk update.
Documentation lives in the core wiki: Framework adapters (shared surface) and Lambda adapter.
- 0.4.0 Frozen re-export thunk over
dynamodb-toolkit/lambda; superseded by the core subpath. No API changes. - 0.3.0 Standalone adapter line (final implementation release); see the core wiki for current docs.
Full details in the wiki's Release notes.