lambder 7.2.0 → 7.2.1

package/CHANGELOG.md

@@ -9,6 +9,19 @@ sit on its first published patch, and later patches list only what they changed.
 Releases up to 3.2.6 carry git tags; the ones after it were published without
 one, so versions are not cross-linked to tag comparisons here.
 
+## [7.2.1] - 2026-09-15
+
+### Added
+
+- **`lambder.apiSignatureEntries()`**: the same signatures `apiSignatures()`
+  returns, each with the endpoint name it was digested from, sorted by key as
+  the map is. The map carries no names, so a generator holding only the map
+  could report that four signatures changed but not which endpoints; reading
+  the entries it can name them. A build-time view by construction: it comes
+  off the server instance, which a generator imports and a client never does.
+  `apiSignatures()` is now this with the names dropped, so there is still one
+  computation. The `LambderApiSignatureEntry` type is exported from the root.
+
 ## [7.1.5] - 2026-09-15
 
 ### Added
@@ -24,7 +37,6 @@ one, so versions are not cross-linked to tag comparisons here.
   warning, so a mistaken floor cannot refuse the build's own clients.
   `compareDottedVersions` and `isDottedVersion` are exported from both
   entries.
-
 ### Changed
 
 - **`apiNameKeyOf` memoizes nothing.** It hashed each name it was asked about

package/dist/api/LambderApiSignature.d.ts

@@ -1,5 +1,18 @@
 import type { LambderApiDefinition } from "./LambderApiDefinition.js";
 import { type LambderApiGuard } from "./LambderApiGuards.js";
+/**
+ * One endpoint as the generator sees it: the key its signature is stored
+ * under, the signature, and the name both were computed from. The name is
+ * what the shipped map deliberately does not carry, so this is the build-time
+ * view of the same data, and the only place a generated map can be diffed by
+ * endpoint rather than by opaque key.
+ */
+export type LambderApiSignatureEntry = {
+    name: string;
+    /** The map key: apiNameKeyOf(name). */
+    key: string;
+    signature: string;
+};
 /**
  * The digest of an endpoint's client-facing shape: its name and mode, its
  * input and output schemas as JSON Schema, every guard it declares with the

package/dist/core/Lambder.d.ts

@@ -9,6 +9,7 @@ import type LambderSessionController from "../session/LambderSessionController.j
 import { type LambderPublicFilesOptions } from "./LambderPublicFiles.js";
 import { type LambderIndexHtmlOptions } from "./LambderIndexHtml.js";
 import { LambderFiles } from "./LambderFiles.js";
+import { type LambderApiSignatureEntry } from "../api/LambderApiSignature.js";
 import { type LambderApiSignatureMap } from "../shared/wire/LambderApiSignature.js";
 import type { LambderApiIdempotencyOption } from "../shared/wire/LambderApiOptionValues.js";
 import type { LambderApiGuard, LambderGuardMetaMap, LambderGuardsOption, LambderGuardDataOf, LambderGuardInputsOf } from "../api/LambderApiGuards.js";
@@ -181,6 +182,18 @@ export default class Lambder<TSessionData = any, _TContract extends Record<strin
      * itself. Keys are sorted, so the generated file diffs by endpoint.
      */
     apiSignatures(): Promise<LambderApiSignatureMap>;
+    /**
+     * The same signatures with the endpoint name each one was digested from,
+     * sorted by key as the map is. What apiSignatures() leaves out on purpose:
+     * the map a client ships lists no names, so a generator that only had the
+     * map could report that four signatures changed but not which endpoints.
+     * Reading this instead, it can name them.
+     *
+     * A build-time view by construction. It comes off the server instance,
+     * which a generator imports and a client never does, so nothing here
+     * reaches a bundle unless the generator writes it there.
+     */
+    apiSignatureEntries(): Promise<LambderApiSignatureEntry[]>;
     getResponseBuilder(ctx?: LambderRenderContext): LambderResponseBuilder<any>;
     private getResolver;
     getHandler(): LambderHandler;

package/dist/core/Lambder.js

@@ -298,9 +298,27 @@ export default class Lambder {
      * itself. Keys are sorted, so the generated file diffs by endpoint.
      */
     async apiSignatures() {
-        const entries = await Promise.all([...this.apiDefinitions.values()].map(async (definition) => [await apiNameKeyOf(definition.name), await apiSignatureOf(definition, this.guards)]));
-        entries.sort(([a], [b]) => (a < b ? -1 : a > b ? 1 : 0));
-        return Object.fromEntries(entries);
+        return Object.fromEntries((await this.apiSignatureEntries()).map(({ key, signature }) => [key, signature]));
+    }
+    /**
+     * The same signatures with the endpoint name each one was digested from,
+     * sorted by key as the map is. What apiSignatures() leaves out on purpose:
+     * the map a client ships lists no names, so a generator that only had the
+     * map could report that four signatures changed but not which endpoints.
+     * Reading this instead, it can name them.
+     *
+     * A build-time view by construction. It comes off the server instance,
+     * which a generator imports and a client never does, so nothing here
+     * reaches a bundle unless the generator writes it there.
+     */
+    async apiSignatureEntries() {
+        const entries = await Promise.all([...this.apiDefinitions.values()].map(async (definition) => ({
+            name: definition.name,
+            key: await apiNameKeyOf(definition.name),
+            signature: await apiSignatureOf(definition, this.guards),
+        })));
+        entries.sort((a, b) => (a.key < b.key ? -1 : a.key > b.key ? 1 : 0));
+        return entries;
     }
     getResponseBuilder(ctx) {
         return new LambderResponseBuilder({

package/dist/index.d.ts

@@ -26,6 +26,7 @@ export { createApiCallContext } from "./api/LambderApiCallContext.js";
 export type { LambderApiCallContext, LambderApiCallTrace } from "./api/LambderApiCallContext.js";
 export type { LambderApiDefinition } from "./api/LambderApiDefinition.js";
 export { apiSignatureOf } from "./api/LambderApiSignature.js";
+export type { LambderApiSignatureEntry } from "./api/LambderApiSignature.js";
 export { apiNameKeyOf, lookupApiSignature, readApiSignature, API_SIGNATURE_HEX_LENGTH } from "./shared/wire/LambderApiSignature.js";
 export type { LambderApiSignatureMap } from "./shared/wire/LambderApiSignature.js";
 export { RELOAD_LOOP_WINDOW_MS } from "./client/LambderReloadLoopBreaker.js";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "lambder",
-  "version": "7.2.0",
+  "version": "7.2.1",
   "sideEffects": false,
   "description": "Opinionated serverless web framework for TypeScript on AWS Lambda: type-safe APIs from Zod schemas, DynamoDB sessions, and declarative rate limits, authorization guards and idempotency.",
   "keywords": [