@kensio/yulin 1.16.0 → 1.16.2

package/dist/service/lambda/function/code/vm/sim-lambda-vm-context.js.map

@@ -1 +1 @@
-{"version":3,"file":"sim-lambda-vm-context.js","sourceRoot":"","sources":["../../../../../../src/service/lambda/function/code/vm/sim-lambda-vm-context.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,OAAO,EAAE,MAAM,cAAc,CAAC;AACvC,OAAO,EAAE,MAAM,SAAS,CAAC;AACzB,OAAO,EAAE,gBAAgB,EAAE,MAAM,6CAA6C,CAAC;AAC/E,OAAO,EAEL,YAAY,GACb,MAAM,wCAAwC,CAAC;AAEhD,OAAO,EACL,qBAAqB,GAEtB,MAAM,yCAAyC,CAAC;AACjD,OAAO,EAAE,uBAAuB,EAAE,MAAM,kCAAkC,CAAC;AAE3E;;;;;;;;;;;;;GAaG;AACH,MAAM,UAAU,sBAAsB,CACpC,WAAiC,EACjC,KAAK,GAAa,IAAI,YAAY,EAAE,EACpC,IAAI,GAAwB,qBAAqB;IAEjD,4EAA4E;IAC5E,2EAA2E;IAC3E,+BAA+B;IAC/B,MAAM,MAAM,GAAG,IAAI,uBAAuB,CAAC,GAAG,EAAE,CAAC,OAAO,CAAC,MAAM,CAAC,CAAC;IACjE,MAAM,MAAM,GAAG,IAAI,uBAAuB,CAAC,GAAG,EAAE,CAAC,OAAO,CAAC,MAAM,CAAC,CAAC;IAEjE,2EAA2E;IAC3E,MAAM,CAAC,QAAQ,CAAC,IAAI,CAAC,CAAC;IACtB,MAAM,CAAC,QAAQ,CAAC,IAAI,CAAC,CAAC;IAEtB,OAAO,EAAE,CAAC,aAAa,CAAC;QACtB,iEAAiE;QACjE,qEAAqE;QACrE,wEAAwE;QACxE,OAAO,EAAE,IAAI,OAAO,CAAC,EAAE,MAAM,EAAE,MAAM,EAAE,CAAC;QACxC,MAAM;QACN,OAAO,EAAE;YACP,GAAG,EAAE,WAAW,CAAC,SAAS,EAAE;YAC5B,MAAM;YACN,MAAM;SACP;QACD,qEAAqE;QACrE,mEAAmE;QACnE,IAAI,EAAE,gBAAgB,CAAC,KAAK,CAAC;QAC7B,UAAU;QACV,YAAY;QACZ,WAAW;QACX,aAAa;QACb,YAAY;QACZ,cAAc;QACd,WAAW;QACX,WAAW;QACX,GAAG;QACH,eAAe;QACf,eAAe;QACf,MAAM;KACP,CAAC,CAAC;AACL,CAAC"}
+{"version":3,"file":"sim-lambda-vm-context.js","sourceRoot":"","sources":["../../../../../../src/service/lambda/function/code/vm/sim-lambda-vm-context.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,OAAO,EAAE,MAAM,cAAc,CAAC;AACvC,OAAO,EAAE,MAAM,SAAS,CAAC;AACzB,OAAO,EAAE,gBAAgB,EAAE,MAAM,6CAA6C,CAAC;AAC/E,OAAO,EAEL,YAAY,GACb,MAAM,wCAAwC,CAAC;AAEhD,OAAO,EACL,qBAAqB,GAEtB,MAAM,yCAAyC,CAAC;AACjD,OAAO,EAAE,0BAA0B,EAAE,MAAM,6CAA6C,CAAC;AAEzF,OAAO,EAAE,uBAAuB,EAAE,MAAM,kCAAkC,CAAC;AAsB3E;;;;;;;;;;;;;;;GAeG;AACH,MAAM,UAAU,sBAAsB,CACpC,UAAwC;IAExC,MAAM,EACJ,WAAW,EACX,KAAK,GAAG,IAAI,YAAY,EAAE,EAC1B,IAAI,GAAG,qBAAqB,EAC5B,YAAY,GACb,GAAG,UAAU,CAAC;IAEf,4EAA4E;IAC5E,2EAA2E;IAC3E,+BAA+B;IAC/B,MAAM,MAAM,GAAG,IAAI,uBAAuB,CAAC,GAAG,EAAE,CAAC,OAAO,CAAC,MAAM,CAAC,CAAC;IACjE,MAAM,MAAM,GAAG,IAAI,uBAAuB,CAAC,GAAG,EAAE,CAAC,OAAO,CAAC,MAAM,CAAC,CAAC;IAEjE,2EAA2E;IAC3E,MAAM,CAAC,QAAQ,CAAC,IAAI,CAAC,CAAC;IACtB,MAAM,CAAC,QAAQ,CAAC,IAAI,CAAC,CAAC;IAEtB,OAAO,EAAE,CAAC,aAAa,CAAC;QACtB,iEAAiE;QACjE,qEAAqE;QACrE,wEAAwE;QACxE,OAAO,EAAE,IAAI,OAAO,CAAC,EAAE,MAAM,EAAE,MAAM,EAAE,CAAC;QACxC,MAAM;QACN,OAAO,EAAE;YACP,GAAG,EAAE,WAAW,CAAC,SAAS,EAAE;YAC5B,MAAM;YACN,MAAM;SACP;QACD,qEAAqE;QACrE,mEAAmE;QACnE,IAAI,EAAE,gBAAgB,CAAC,KAAK,CAAC;QAC7B,UAAU;QACV,YAAY;QACZ,WAAW;QACX,aAAa;QACb,YAAY;QACZ,cAAc;QACd,WAAW;QACX,WAAW;QACX,GAAG;QACH,eAAe;QACf,eAAe;QACf,MAAM;QACN,qEAAqE;QACrE,0EAA0E;QAC1E,yEAAyE;QACzE,iBAAiB;QACjB,KAAK,EAAE,0BAA0B,CAAC,YAAY,CAAC;QAC/C,OAAO;QACP,OAAO;QACP,QAAQ;QACR,QAAQ;QACR,IAAI;QACJ,eAAe;QACf,WAAW;KACZ,CAAC,CAAC;AACL,CAAC"}

package/dist/service/lambda/function/invoke/sim-lambda-host-scope.d.ts

@@ -0,0 +1,26 @@
+import type { SimClock } from "../../../../util/clock/sim-clock.js";
+import type { SimLambdaOutboundHttp } from "../outbound/sim-lambda-outbound-http.js";
+/**
+ * What an invocation of host-scope code has bridged to it.
+ */
+interface SimLambdaHostScope {
+    /** The time the invocation reports as the current time. */
+    readonly clock: SimClock;
+    /**
+     * Where the requests the invocation makes to hostnames the simulation
+     * serves are answered. A function outside a simulated environment has none,
+     * and its requests go where they were addressed.
+     */
+    readonly outboundHttp: SimLambdaOutboundHttp | undefined;
+}
+/**
+ * Run an invocation of code in the host scope with the process globals it
+ * reads bridged to its simulation.
+ *
+ * Only code running in the host scope needs this. Zip code reads the Date and
+ * the HTTP clients its own vm sandbox was given, so a function backed by one
+ * leaves the globals alone entirely and never comes here.
+ */
+export declare function runSimLambdaInHostScope<T>(scope: SimLambdaHostScope, run: () => Promise<T>): Promise<T>;
+export {};
+//# sourceMappingURL=sim-lambda-host-scope.d.ts.map

package/dist/service/lambda/function/invoke/sim-lambda-host-scope.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"sim-lambda-host-scope.d.ts","sourceRoot":"","sources":["../../../../../src/service/lambda/function/invoke/sim-lambda-host-scope.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,QAAQ,EAAE,MAAM,qCAAqC,CAAC;AACpE,OAAO,KAAK,EAAE,qBAAqB,EAAE,MAAM,yCAAyC,CAAC;AAIrF;;GAEG;AACH,UAAU,kBAAkB;IAC1B,2DAA2D;IAC3D,QAAQ,CAAC,KAAK,EAAE,QAAQ,CAAC;IAEzB;;;;OAIG;IACH,QAAQ,CAAC,YAAY,EAAE,qBAAqB,GAAG,SAAS,CAAC;CAC1D;AAED;;;;;;;GAOG;AACH,wBAAsB,uBAAuB,CAAC,CAAC,EAC7C,KAAK,EAAE,kBAAkB,EACzB,GAAG,EAAE,MAAM,OAAO,CAAC,CAAC,CAAC,GACpB,OAAO,CAAC,CAAC,CAAC,CAQZ"}

package/dist/service/lambda/function/invoke/sim-lambda-host-scope.js

@@ -0,0 +1,17 @@
+import { simLambdaProcessClock } from "./sim-lambda-process-clock.js";
+import { simLambdaProcessOutbound } from "./sim-lambda-process-outbound.js";
+/**
+ * Run an invocation of code in the host scope with the process globals it
+ * reads bridged to its simulation.
+ *
+ * Only code running in the host scope needs this. Zip code reads the Date and
+ * the HTTP clients its own vm sandbox was given, so a function backed by one
+ * leaves the globals alone entirely and never comes here.
+ */
+export async function runSimLambdaInHostScope(scope, run) {
+    const { outboundHttp } = scope;
+    return await simLambdaProcessClock.run(scope.clock, async () => outboundHttp === undefined
+        ? await run()
+        : await simLambdaProcessOutbound.run(outboundHttp, run));
+}
+//# sourceMappingURL=sim-lambda-host-scope.js.map

package/dist/service/lambda/function/invoke/sim-lambda-host-scope.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"sim-lambda-host-scope.js","sourceRoot":"","sources":["../../../../../src/service/lambda/function/invoke/sim-lambda-host-scope.ts"],"names":[],"mappings":"AAEA,OAAO,EAAE,qBAAqB,EAAE,MAAM,+BAA+B,CAAC;AACtE,OAAO,EAAE,wBAAwB,EAAE,MAAM,kCAAkC,CAAC;AAiB5E;;;;;;;GAOG;AACH,MAAM,CAAC,KAAK,UAAU,uBAAuB,CAC3C,KAAyB,EACzB,GAAqB;IAErB,MAAM,EAAE,YAAY,EAAE,GAAG,KAAK,CAAC;IAE/B,OAAO,MAAM,qBAAqB,CAAC,GAAG,CAAC,KAAK,CAAC,KAAK,EAAE,KAAK,IAAI,EAAE,CAC7D,YAAY,KAAK,SAAS;QACxB,CAAC,CAAC,MAAM,GAAG,EAAE;QACb,CAAC,CAAC,MAAM,wBAAwB,CAAC,GAAG,CAAC,YAAY,EAAE,GAAG,CAAC,CAC1D,CAAC;AACJ,CAAC"}

package/dist/service/lambda/function/invoke/sim-lambda-outbound-clients.d.ts

@@ -0,0 +1,17 @@
+import type { SimLambdaOutboundHttp } from "../outbound/sim-lambda-outbound-http.js";
+/**
+ * Replace the process-wide HTTP clients with ones an outbound HTTP answers
+ * for.
+ *
+ * The global `fetch` is defined rather than assigned, to keep it the
+ * configurable, writable, non-enumerable global property it already was:
+ * anything else replacing it has to find what it expects.
+ *
+ * The transport modules are what a handler holds, so the two functions that
+ * start a request are replaced on them in place, leaving everything else the
+ * modules export as it was. The built-in modules' named ES module exports are
+ * a snapshot of those properties, so they are re-synchronised afterwards for
+ * the handler that imported `request` by name rather than the module.
+ */
+export declare function installSimLambdaOutboundClients(outbound: SimLambdaOutboundHttp): void;
+//# sourceMappingURL=sim-lambda-outbound-clients.d.ts.map

package/dist/service/lambda/function/invoke/sim-lambda-outbound-clients.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"sim-lambda-outbound-clients.d.ts","sourceRoot":"","sources":["../../../../../src/service/lambda/function/invoke/sim-lambda-outbound-clients.ts"],"names":[],"mappings":"AAKA,OAAO,KAAK,EAAE,qBAAqB,EAAE,MAAM,yCAAyC,CAAC;AAWrF;;;;;;;;;;;;;GAaG;AACH,wBAAgB,+BAA+B,CAC7C,QAAQ,EAAE,qBAAqB,GAC9B,IAAI,CAkBN"}

package/dist/service/lambda/function/invoke/sim-lambda-outbound-clients.js

@@ -0,0 +1,43 @@
+import http from "node:http";
+import https from "node:https";
+import { syncBuiltinESMExports } from "node:module";
+import { makeSimLambdaHttpModule } from "../outbound/sim-lambda-http-module.js";
+import { makeSimLambdaOutboundFetch } from "../outbound/sim-lambda-outbound-fetch.js";
+/**
+ * The transport modules an in-process handler makes requests through, with the
+ * scheme each one carries.
+ */
+const transportModules = [
+    [http, "http:"],
+    [https, "https:"],
+];
+/**
+ * Replace the process-wide HTTP clients with ones an outbound HTTP answers
+ * for.
+ *
+ * The global `fetch` is defined rather than assigned, to keep it the
+ * configurable, writable, non-enumerable global property it already was:
+ * anything else replacing it has to find what it expects.
+ *
+ * The transport modules are what a handler holds, so the two functions that
+ * start a request are replaced on them in place, leaving everything else the
+ * modules export as it was. The built-in modules' named ES module exports are
+ * a snapshot of those properties, so they are re-synchronised afterwards for
+ * the handler that imported `request` by name rather than the module.
+ */
+export function installSimLambdaOutboundClients(outbound) {
+    const hostFetch = globalThis.fetch;
+    Object.defineProperty(globalThis, "fetch", {
+        configurable: true,
+        writable: true,
+        value: makeSimLambdaOutboundFetch(outbound, hostFetch),
+    });
+    for (const [hostModule, scheme] of transportModules) {
+        const routed = makeSimLambdaHttpModule({ hostModule, outbound, scheme });
+        const patched = hostModule;
+        patched["request"] = routed["request"];
+        patched["get"] = routed["get"];
+    }
+    syncBuiltinESMExports();
+}
+//# sourceMappingURL=sim-lambda-outbound-clients.js.map

package/dist/service/lambda/function/invoke/sim-lambda-outbound-clients.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"sim-lambda-outbound-clients.js","sourceRoot":"","sources":["../../../../../src/service/lambda/function/invoke/sim-lambda-outbound-clients.ts"],"names":[],"mappings":"AAAA,OAAO,IAAI,MAAM,WAAW,CAAC;AAC7B,OAAO,KAAK,MAAM,YAAY,CAAC;AAC/B,OAAO,EAAE,qBAAqB,EAAE,MAAM,aAAa,CAAC;AACpD,OAAO,EAAE,uBAAuB,EAAE,MAAM,uCAAuC,CAAC;AAChF,OAAO,EAAE,0BAA0B,EAAE,MAAM,0CAA0C,CAAC;AAGtF;;;GAGG;AACH,MAAM,gBAAgB,GAAG;IACvB,CAAC,IAAI,EAAE,OAAO,CAAC;IACf,CAAC,KAAK,EAAE,QAAQ,CAAC;CACT,CAAC;AAEX;;;;;;;;;;;;;GAaG;AACH,MAAM,UAAU,+BAA+B,CAC7C,QAA+B;IAE/B,MAAM,SAAS,GAAG,UAAU,CAAC,KAAK,CAAC;IAEnC,MAAM,CAAC,cAAc,CAAC,UAAU,EAAE,OAAO,EAAE;QACzC,YAAY,EAAE,IAAI;QAClB,QAAQ,EAAE,IAAI;QACd,KAAK,EAAE,0BAA0B,CAAC,QAAQ,EAAE,SAAS,CAAC;KACvD,CAAC,CAAC;IAEH,KAAK,MAAM,CAAC,UAAU,EAAE,MAAM,CAAC,IAAI,gBAAgB,EAAE,CAAC;QACpD,MAAM,MAAM,GAAG,uBAAuB,CAAC,EAAE,UAAU,EAAE,QAAQ,EAAE,MAAM,EAAE,CAAC,CAAC;QACzE,MAAM,OAAO,GAAG,UAAgD,CAAC;QAEjE,OAAO,CAAC,SAAS,CAAC,GAAG,MAAM,CAAC,SAAS,CAAC,CAAC;QACvC,OAAO,CAAC,KAAK,CAAC,GAAG,MAAM,CAAC,KAAK,CAAC,CAAC;IACjC,CAAC;IAED,qBAAqB,EAAE,CAAC;AAC1B,CAAC"}

package/dist/service/lambda/function/invoke/sim-lambda-process-outbound.d.ts

@@ -0,0 +1,44 @@
+import type { SimLambdaOutboundHttp } from "../outbound/sim-lambda-outbound-http.js";
+/**
+ * Where the HTTP clients an in-process sim Lambda handler uses are routed to
+ * the simulation it belongs to.
+ *
+ * A handler backed by a real in-process function is a closure over its own
+ * module scope, so it reaches for the same `fetch`, `node:http` and
+ * `node:https` as everything else in the test run. Zip code is handed clients
+ * of its own by the sandbox and needs none of this. Node.js asynchronous
+ * context tracking bridges the gap, exactly as it does for process.env and the
+ * clock: the invocation's outbound HTTP is held in an AsyncLocalStorage store,
+ * and the patched clients resolve to it while it is set.
+ *
+ * The store follows the invocation across await points, so concurrent
+ * invocations of functions belonging to different simulations each reach their
+ * own.
+ */
+declare class SimLambdaProcessOutbound {
+    private readonly storage;
+    private installed;
+    /**
+     * Run an invocation with the given outbound HTTP answering the requests its
+     * code makes to hostnames the simulation serves.
+     */
+    run<T>(outbound: SimLambdaOutboundHttp, run: () => Promise<T>): Promise<T>;
+    /**
+     * Replace the process-wide HTTP clients with ones backed by the invocation
+     * store.
+     *
+     * Installed on the first invocation of an in-process handler rather than at
+     * import, so a test run that never uses one is left completely alone. With
+     * no invocation running the patched clients hand every request to the host
+     * client, so an installed patch behaves exactly like no patch at all. They
+     * are never removed: removing them would be unsafe while another invocation
+     * is in flight, and there is nothing to gain.
+     */
+    private install;
+}
+/**
+ * Shared because it patches process globals: one patch, one store.
+ */
+export declare const simLambdaProcessOutbound: SimLambdaProcessOutbound;
+export {};
+//# sourceMappingURL=sim-lambda-process-outbound.d.ts.map

package/dist/service/lambda/function/invoke/sim-lambda-process-outbound.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"sim-lambda-process-outbound.d.ts","sourceRoot":"","sources":["../../../../../src/service/lambda/function/invoke/sim-lambda-process-outbound.ts"],"names":[],"mappings":"AAEA,OAAO,KAAK,EAAE,qBAAqB,EAAE,MAAM,yCAAyC,CAAC;AAuCrF;;;;;;;;;;;;;;;GAeG;AACH,cAAM,wBAAwB;IAC5B,OAAO,CAAC,QAAQ,CAAC,OAAO,CAAkD;IAC1E,OAAO,CAAC,SAAS,CAAS;IAE1B;;;OAGG;IACG,GAAG,CAAC,CAAC,EACT,QAAQ,EAAE,qBAAqB,EAC/B,GAAG,EAAE,MAAM,OAAO,CAAC,CAAC,CAAC,GACpB,OAAO,CAAC,CAAC,CAAC,CAGZ;IAED;;;;;;;;;;OAUG;IACH,OAAO,CAAC,OAAO;CAQhB;AAED;;GAEG;AACH,eAAO,MAAM,wBAAwB,0BAAiC,CAAC"}

package/dist/service/lambda/function/invoke/sim-lambda-process-outbound.js

@@ -0,0 +1,83 @@
+import { AsyncLocalStorage } from "node:async_hooks";
+import { assertDefined } from "../../../../util/type-guard/defined.js";
+import { installSimLambdaOutboundClients } from "./sim-lambda-outbound-clients.js";
+/**
+ * The outbound HTTP the patched clients route through.
+ *
+ * An invocation in progress lends its own; anything else in the process
+ * reaches the network as it always did, which is what keeps the patches inert
+ * outside a sim Lambda invocation.
+ */
+class SimLambdaAmbientOutbound {
+    storage;
+    constructor(storage) {
+        this.storage = storage;
+    }
+    /**
+     * Whether the invocation in progress, if there is one, serves a hostname.
+     */
+    serves(hostname) {
+        return this.storage.getStore()?.serves(hostname) ?? false;
+    }
+    /**
+     * Answer a request from the invocation in progress.
+     */
+    async fetch(request) {
+        const outbound = this.storage.getStore();
+        /* v8 ignore next 4 -- only reached for a request `serves` accepted, which
+           is a request made while an invocation is in progress. */
+        assertDefined(outbound, "sim Lambda invocation outbound HTTP for a request the simulation serves");
+        return await outbound.fetch(request);
+    }
+}
+/**
+ * Where the HTTP clients an in-process sim Lambda handler uses are routed to
+ * the simulation it belongs to.
+ *
+ * A handler backed by a real in-process function is a closure over its own
+ * module scope, so it reaches for the same `fetch`, `node:http` and
+ * `node:https` as everything else in the test run. Zip code is handed clients
+ * of its own by the sandbox and needs none of this. Node.js asynchronous
+ * context tracking bridges the gap, exactly as it does for process.env and the
+ * clock: the invocation's outbound HTTP is held in an AsyncLocalStorage store,
+ * and the patched clients resolve to it while it is set.
+ *
+ * The store follows the invocation across await points, so concurrent
+ * invocations of functions belonging to different simulations each reach their
+ * own.
+ */
+class SimLambdaProcessOutbound {
+    storage = new AsyncLocalStorage();
+    installed = false;
+    /**
+     * Run an invocation with the given outbound HTTP answering the requests its
+     * code makes to hostnames the simulation serves.
+     */
+    async run(outbound, run) {
+        this.install();
+        return await this.storage.run(outbound, run);
+    }
+    /**
+     * Replace the process-wide HTTP clients with ones backed by the invocation
+     * store.
+     *
+     * Installed on the first invocation of an in-process handler rather than at
+     * import, so a test run that never uses one is left completely alone. With
+     * no invocation running the patched clients hand every request to the host
+     * client, so an installed patch behaves exactly like no patch at all. They
+     * are never removed: removing them would be unsafe while another invocation
+     * is in flight, and there is nothing to gain.
+     */
+    install() {
+        if (this.installed) {
+            return;
+        }
+        this.installed = true;
+        installSimLambdaOutboundClients(new SimLambdaAmbientOutbound(this.storage));
+    }
+}
+/**
+ * Shared because it patches process globals: one patch, one store.
+ */
+export const simLambdaProcessOutbound = new SimLambdaProcessOutbound();
+//# sourceMappingURL=sim-lambda-process-outbound.js.map

package/dist/service/lambda/function/invoke/sim-lambda-process-outbound.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"sim-lambda-process-outbound.js","sourceRoot":"","sources":["../../../../../src/service/lambda/function/invoke/sim-lambda-process-outbound.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,iBAAiB,EAAE,MAAM,kBAAkB,CAAC;AACrD,OAAO,EAAE,aAAa,EAAE,MAAM,wCAAwC,CAAC;AAEvE,OAAO,EAAE,+BAA+B,EAAE,MAAM,kCAAkC,CAAC;AAEnF;;;;;;GAMG;AACH,MAAM,wBAAwB;IAET,OAAO;IAD1B,YACmB,OAAiD;uBAAjD,OAAO;IACvB,CAAC;IAEJ;;OAEG;IACH,MAAM,CAAC,QAAgB;QACrB,OAAO,IAAI,CAAC,OAAO,CAAC,QAAQ,EAAE,EAAE,MAAM,CAAC,QAAQ,CAAC,IAAI,KAAK,CAAC;IAC5D,CAAC;IAED;;OAEG;IACH,KAAK,CAAC,KAAK,CAAC,OAAgB;QAC1B,MAAM,QAAQ,GAAG,IAAI,CAAC,OAAO,CAAC,QAAQ,EAAE,CAAC;QAEzC;mEAC2D;QAC3D,aAAa,CACX,QAAQ,EACR,yEAAyE,CAC1E,CAAC;QAEF,OAAO,MAAM,QAAQ,CAAC,KAAK,CAAC,OAAO,CAAC,CAAC;IACvC,CAAC;CACF;AAED;;;;;;;;;;;;;;;GAeG;AACH,MAAM,wBAAwB;IACX,OAAO,GAAG,IAAI,iBAAiB,EAAyB,CAAC;IAClE,SAAS,GAAG,KAAK,CAAC;IAE1B;;;OAGG;IACH,KAAK,CAAC,GAAG,CACP,QAA+B,EAC/B,GAAqB;QAErB,IAAI,CAAC,OAAO,EAAE,CAAC;QACf,OAAO,MAAM,IAAI,CAAC,OAAO,CAAC,GAAG,CAAC,QAAQ,EAAE,GAAG,CAAC,CAAC;IAC/C,CAAC;IAED;;;;;;;;;;OAUG;IACK,OAAO;QACb,IAAI,IAAI,CAAC,SAAS,EAAE,CAAC;YACnB,OAAO;QACT,CAAC;QACD,IAAI,CAAC,SAAS,GAAG,IAAI,CAAC;QAEtB,+BAA+B,CAAC,IAAI,wBAAwB,CAAC,IAAI,CAAC,OAAO,CAAC,CAAC,CAAC;IAC9E,CAAC;CACF;AAED;;GAEG;AACH,MAAM,CAAC,MAAM,wBAAwB,GAAG,IAAI,wBAAwB,EAAE,CAAC"}

package/dist/service/lambda/function/outbound/sim-lambda-aws-api-outbound.d.ts

@@ -0,0 +1,50 @@
+import type { AwsRegionName } from "../../../aws/sim-aws-region.js";
+import type { SimAws } from "../../../aws/sim-aws.js";
+import type { SimLambdaOutboundHttp } from "./sim-lambda-outbound-http.js";
+/**
+ * Whether a hostname is an AWS service API endpoint.
+ */
+export declare function isSimAwsEndpointHostname(hostname: string): boolean;
+/**
+ * Whether a request to an AWS service API endpoint is an API call, or an
+ * ordinary HTTP request to the same hostname.
+ *
+ * A service API endpoint answers both. What an SDK sends carries the operation
+ * header of the AWS JSON protocol, or the SigV4 credentials it was signed
+ * with, or both, and the wire dispatcher answers it. A token verifier fetching
+ * from the same hostname carries neither, because it holds nothing to sign
+ * with. A user pool publishes its JWKS and its OpenID configuration to whoever
+ * asks, and both are read over plain HTTP.
+ */
+export declare function isSimAwsApiRequest(request: Request): boolean;
+interface SimLambdaAwsApiOutboundProperties {
+    readonly simAws: SimAws;
+    /**
+     * The Region the function code is running in, which answers a request whose
+     * credential scope names none.
+     */
+    readonly regionName?: AwsRegionName | undefined;
+}
+/**
+ * Answers the AWS service API requests sim Lambda function code sends.
+ *
+ * This is the half of a function's outbound HTTP that carries a serialized
+ * Command rather than an ordinary HTTP request: the SDK has already signed and
+ * encoded it by the time it reaches a transport, so the request itself is what
+ * there is to route, and the wire dispatcher turns it back into the simulated
+ * operation it names.
+ */
+export declare class SimLambdaAwsApiOutbound implements SimLambdaOutboundHttp {
+    private readonly dispatcher;
+    constructor(properties: SimLambdaAwsApiOutboundProperties);
+    /**
+     * Whether a hostname is one of the AWS service API endpoints.
+     */
+    serves(hostname: string): boolean;
+    /**
+     * Answer an AWS API request from the simulated operation it names.
+     */
+    fetch(request: Request): Promise<Response>;
+}
+export {};
+//# sourceMappingURL=sim-lambda-aws-api-outbound.d.ts.map

package/dist/service/lambda/function/outbound/sim-lambda-aws-api-outbound.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"sim-lambda-aws-api-outbound.d.ts","sourceRoot":"","sources":["../../../../../src/service/lambda/function/outbound/sim-lambda-aws-api-outbound.ts"],"names":[],"mappings":"AAKA,OAAO,KAAK,EAAE,aAAa,EAAE,MAAM,gCAAgC,CAAC;AACpE,OAAO,KAAK,EAAE,MAAM,EAAE,MAAM,yBAAyB,CAAC;AACtD,OAAO,KAAK,EAAE,qBAAqB,EAAE,MAAM,+BAA+B,CAAC;AAkC3E;;GAEG;AACH,wBAAgB,wBAAwB,CAAC,QAAQ,EAAE,MAAM,GAAG,OAAO,CAQlE;AAED;;;;;;;;;;GAUG;AACH,wBAAgB,kBAAkB,CAAC,OAAO,EAAE,OAAO,GAAG,OAAO,CAO5D;AAED,UAAU,iCAAiC;IACzC,QAAQ,CAAC,MAAM,EAAE,MAAM,CAAC;IAExB;;;OAGG;IACH,QAAQ,CAAC,UAAU,CAAC,EAAE,aAAa,GAAG,SAAS,CAAC;CACjD;AAED;;;;;;;;GAQG;AACH,qBAAa,uBAAwB,YAAW,qBAAqB;IACnE,OAAO,CAAC,QAAQ,CAAC,UAAU,CAAuB;IAElD,YAAY,UAAU,EAAE,iCAAiC,EAKxD;IAED;;OAEG;IACH,MAAM,CAAC,QAAQ,EAAE,MAAM,GAAG,OAAO,CAEhC;IAED;;OAEG;IACG,KAAK,CAAC,OAAO,EAAE,OAAO,GAAG,OAAO,CAAC,QAAQ,CAAC,CAM/C;CACF"}

package/dist/service/lambda/function/outbound/sim-lambda-aws-api-outbound.js

@@ -0,0 +1,83 @@
+import { SimSdkWireDispatcher } from "../../../../sdk/wire/sim-sdk-wire-dispatcher.js";
+import { readSimSdkWireCredentialScope, readSimSdkWireOperation, } from "../../../../sdk/wire/sim-sdk-wire-operation.js";
+import { simLambdaOutboundWireRequest, simLambdaOutboundWireResponse, } from "./sim-lambda-outbound-wire.js";
+/**
+ * The hostname suffixes AWS issues its service API endpoints under.
+ *
+ * A request to one of these is a request to an AWS service API whoever sent
+ * it, so it belongs to the simulation rather than the network. Everything else
+ * a function asks for is either a hostname the simulation serves some other
+ * way or one it serves nothing at.
+ *
+ * `.on.aws` is not among them: what AWS issues under it is Lambda Function
+ * URLs, which are the endpoint of one function rather than a service API.
+ */
+const awsEndpointSuffixes = [
+    ".amazonaws.com",
+    ".amazonaws.com.cn",
+    ".api.aws",
+];
+/**
+ * The label an endpoint hostname carries when it names one resource rather
+ * than a service API: an API Gateway HTTP API, under `.amazonaws.com`.
+ *
+ * A request to one of these is an ordinary HTTP request to something the
+ * simulation may be running, not a serialized Command, so there is nothing
+ * here to route it as. Simulated Route53 answers for it instead, in the same
+ * way it answers for every other hostname a resource is issued.
+ */
+const resourceEndpointLabel = ".execute-api.";
+/**
+ * Whether a hostname is an AWS service API endpoint.
+ */
+export function isSimAwsEndpointHostname(hostname) {
+    const name = hostname.toLowerCase();
+    if (name.includes(resourceEndpointLabel)) {
+        return false;
+    }
+    return awsEndpointSuffixes.some((suffix) => name.endsWith(suffix));
+}
+/**
+ * Whether a request to an AWS service API endpoint is an API call, or an
+ * ordinary HTTP request to the same hostname.
+ *
+ * A service API endpoint answers both. What an SDK sends carries the operation
+ * header of the AWS JSON protocol, or the SigV4 credentials it was signed
+ * with, or both, and the wire dispatcher answers it. A token verifier fetching
+ * from the same hostname carries neither, because it holds nothing to sign
+ * with. A user pool publishes its JWKS and its OpenID configuration to whoever
+ * asks, and both are read over plain HTTP.
+ */
+export function isSimAwsApiRequest(request) {
+    const wireRequest = { headers: Object.fromEntries(request.headers) };
+    return (readSimSdkWireOperation(wireRequest) !== undefined ||
+        readSimSdkWireCredentialScope(wireRequest) !== undefined);
+}
+/**
+ * Answers the AWS service API requests sim Lambda function code sends.
+ *
+ * This is the half of a function's outbound HTTP that carries a serialized
+ * Command rather than an ordinary HTTP request: the SDK has already signed and
+ * encoded it by the time it reaches a transport, so the request itself is what
+ * there is to route, and the wire dispatcher turns it back into the simulated
+ * operation it names.
+ */
+export class SimLambdaAwsApiOutbound {
+    dispatcher;
+    constructor(properties) {
+        this.dispatcher = new SimSdkWireDispatcher(properties.simAws, properties.regionName);
+    }
+    /**
+     * Whether a hostname is one of the AWS service API endpoints.
+     */
+    serves(hostname) {
+        return isSimAwsEndpointHostname(hostname);
+    }
+    /**
+     * Answer an AWS API request from the simulated operation it names.
+     */
+    async fetch(request) {
+        return simLambdaOutboundWireResponse(await this.dispatcher.dispatch(await simLambdaOutboundWireRequest(request)));
+    }
+}
+//# sourceMappingURL=sim-lambda-aws-api-outbound.js.map

package/dist/service/lambda/function/outbound/sim-lambda-aws-api-outbound.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"sim-lambda-aws-api-outbound.js","sourceRoot":"","sources":["../../../../../src/service/lambda/function/outbound/sim-lambda-aws-api-outbound.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,oBAAoB,EAAE,MAAM,iDAAiD,CAAC;AACvF,OAAO,EACL,6BAA6B,EAC7B,uBAAuB,GACxB,MAAM,gDAAgD,CAAC;AAIxD,OAAO,EACL,4BAA4B,EAC5B,6BAA6B,GAC9B,MAAM,+BAA+B,CAAC;AAEvC;;;;;;;;;;GAUG;AACH,MAAM,mBAAmB,GAAsB;IAC7C,gBAAgB;IAChB,mBAAmB;IACnB,UAAU;CACX,CAAC;AAEF;;;;;;;;GAQG;AACH,MAAM,qBAAqB,GAAG,eAAe,CAAC;AAE9C;;GAEG;AACH,MAAM,UAAU,wBAAwB,CAAC,QAAgB;IACvD,MAAM,IAAI,GAAG,QAAQ,CAAC,WAAW,EAAE,CAAC;IAEpC,IAAI,IAAI,CAAC,QAAQ,CAAC,qBAAqB,CAAC,EAAE,CAAC;QACzC,OAAO,KAAK,CAAC;IACf,CAAC;IAED,OAAO,mBAAmB,CAAC,IAAI,CAAC,CAAC,MAAM,EAAE,EAAE,CAAC,IAAI,CAAC,QAAQ,CAAC,MAAM,CAAC,CAAC,CAAC;AACrE,CAAC;AAED;;;;;;;;;;GAUG;AACH,MAAM,UAAU,kBAAkB,CAAC,OAAgB;IACjD,MAAM,WAAW,GAAG,EAAE,OAAO,EAAE,MAAM,CAAC,WAAW,CAAC,OAAO,CAAC,OAAO,CAAC,EAAE,CAAC;IAErE,OAAO,CACL,uBAAuB,CAAC,WAAW,CAAC,KAAK,SAAS;QAClD,6BAA6B,CAAC,WAAW,CAAC,KAAK,SAAS,CACzD,CAAC;AACJ,CAAC;AAYD;;;;;;;;GAQG;AACH,MAAM,OAAO,uBAAuB;IACjB,UAAU,CAAuB;IAElD,YAAY,UAA6C;QACvD,IAAI,CAAC,UAAU,GAAG,IAAI,oBAAoB,CACxC,UAAU,CAAC,MAAM,EACjB,UAAU,CAAC,UAAU,CACtB,CAAC;IACJ,CAAC;IAED;;OAEG;IACH,MAAM,CAAC,QAAgB;QACrB,OAAO,wBAAwB,CAAC,QAAQ,CAAC,CAAC;IAC5C,CAAC;IAED;;OAEG;IACH,KAAK,CAAC,KAAK,CAAC,OAAgB;QAC1B,OAAO,6BAA6B,CAClC,MAAM,IAAI,CAAC,UAAU,CAAC,QAAQ,CAC5B,MAAM,4BAA4B,CAAC,OAAO,CAAC,CAC5C,CACF,CAAC;IACJ,CAAC;CACF"}

package/dist/service/lambda/function/outbound/sim-lambda-http-module.d.ts

@@ -0,0 +1,42 @@
+import type { SimLambdaOutboundHttp } from "./sim-lambda-outbound-http.js";
+/**
+ * A `node:http` or `node:https` module, as far as this needs to know.
+ */
+type NodeHttpModule = Record<string, unknown>;
+/**
+ * Whether a module specifier names an HTTP transport module.
+ */
+export declare function isSimLambdaHttpModuleSpecifier(specifier: string): boolean;
+/**
+ * The scheme a transport module's requests are made with, for a specifier
+ * naming one.
+ */
+export declare function simLambdaHttpModuleScheme(specifier: string): string;
+interface SimLambdaHttpModuleProperties {
+    readonly hostModule: NodeHttpModule;
+    readonly outbound: SimLambdaOutboundHttp;
+    /**
+     * The scheme this module's requests carry, `https:` unless said otherwise,
+     * since the arguments to a request rarely name one.
+     */
+    readonly scheme?: string | undefined;
+}
+/**
+ * Build the `node:http` or `node:https` module sim Lambda function code makes
+ * its requests through.
+ *
+ * Everything the real module exports is kept, and only the two functions that
+ * start a request are replaced, so a client library that reaches for an Agent,
+ * a status code table or anything else finds the real thing. A request to a
+ * hostname the simulation serves is answered by the simulation; every other
+ * request is the host module's, made exactly as it was asked for.
+ *
+ * This is where a deployment package that bundles the AWS SDK is reached. The
+ * bundled SDK resolves no module specifier the simulator can intercept, but it
+ * still asks the runtime for its HTTP transport, and that is a module the
+ * runtime provides. It is also what a handler reaching for `node:https`
+ * directly gets, which an OAuth token exchange written without `fetch` does.
+ */
+export declare function makeSimLambdaHttpModule(properties: SimLambdaHttpModuleProperties): NodeHttpModule;
+export {};
+//# sourceMappingURL=sim-lambda-http-module.d.ts.map

package/dist/service/lambda/function/outbound/sim-lambda-http-module.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"sim-lambda-http-module.d.ts","sourceRoot":"","sources":["../../../../../src/service/lambda/function/outbound/sim-lambda-http-module.ts"],"names":[],"mappings":"AAEA,OAAO,KAAK,EAAE,qBAAqB,EAAE,MAAM,+BAA+B,CAAC;AAE3E;;GAEG;AACH,KAAK,cAAc,GAAG,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,CAAC;AAc9C;;GAEG;AACH,wBAAgB,8BAA8B,CAAC,SAAS,EAAE,MAAM,GAAG,OAAO,CAEzE;AAED;;;GAGG;AACH,wBAAgB,yBAAyB,CAAC,SAAS,EAAE,MAAM,GAAG,MAAM,CAEnE;AAID,UAAU,6BAA6B;IACrC,QAAQ,CAAC,UAAU,EAAE,cAAc,CAAC;IACpC,QAAQ,CAAC,QAAQ,EAAE,qBAAqB,CAAC;IAEzC;;;OAGG;IACH,QAAQ,CAAC,MAAM,CAAC,EAAE,MAAM,GAAG,SAAS,CAAC;CACtC;AAED;;;;;;;;;;;;;;;GAeG;AACH,wBAAgB,uBAAuB,CACrC,UAAU,EAAE,6BAA6B,GACxC,cAAc,CA0BhB"}

package/dist/service/lambda/function/outbound/sim-lambda-http-module.js

@@ -0,0 +1,88 @@
+import { SimLambdaHttpRequest } from "./sim-lambda-http-request.js";
+import { readSimLambdaHttpTarget } from "./sim-lambda-http-target.js";
+/**
+ * The transport modules an SDK bundled into the function code archive reaches
+ * the network through, named as both a bundler and a hand-written require may
+ * ask for them, with the scheme each one carries.
+ */
+const httpModuleSchemes = new Map([
+    ["http", "http:"],
+    ["node:http", "http:"],
+    ["https", "https:"],
+    ["node:https", "https:"],
+]);
+/**
+ * Whether a module specifier names an HTTP transport module.
+ */
+export function isSimLambdaHttpModuleSpecifier(specifier) {
+    return httpModuleSchemes.has(specifier);
+}
+/**
+ * The scheme a transport module's requests are made with, for a specifier
+ * naming one.
+ */
+export function simLambdaHttpModuleScheme(specifier) {
+    return httpModuleSchemes.get(specifier) ?? "https:";
+}
+/**
+ * Build the `node:http` or `node:https` module sim Lambda function code makes
+ * its requests through.
+ *
+ * Everything the real module exports is kept, and only the two functions that
+ * start a request are replaced, so a client library that reaches for an Agent,
+ * a status code table or anything else finds the real thing. A request to a
+ * hostname the simulation serves is answered by the simulation; every other
+ * request is the host module's, made exactly as it was asked for.
+ *
+ * This is where a deployment package that bundles the AWS SDK is reached. The
+ * bundled SDK resolves no module specifier the simulator can intercept, but it
+ * still asks the runtime for its HTTP transport, and that is a module the
+ * runtime provides. It is also what a handler reaching for `node:https`
+ * directly gets, which an OAuth token exchange written without `fetch` does.
+ */
+export function makeSimLambdaHttpModule(properties) {
+    const { hostModule } = properties;
+    const hostRequest = hostModule["request"];
+    const hostGet = hostModule["get"];
+    return {
+        ...hostModule,
+        request: (...callArguments) => {
+            const simulated = simulatedRequest(callArguments, properties);
+            return simulated ?? hostRequest(...callArguments);
+        },
+        /**
+         * `get` is `request` with the body ended immediately, which is the whole
+         * of the difference for a request the simulation answers.
+         */
+        get: (...callArguments) => {
+            const simulated = simulatedRequest(callArguments, properties);
+            if (simulated === undefined) {
+                return hostGet(...callArguments);
+            }
+            simulated.end();
+            return simulated;
+        },
+    };
+}
+/**
+ * Start a simulated request, for a call addressed to a hostname the simulation
+ * serves.
+ *
+ * The response callback a caller passed is attached to the `response` event,
+ * as the real module attaches it, so a caller using either receives the
+ * response.
+ */
+function simulatedRequest(callArguments, properties) {
+    const { outbound, scheme = "https:" } = properties;
+    const target = readSimLambdaHttpTarget(callArguments);
+    if (target === undefined || !outbound.serves(target.hostname)) {
+        return undefined;
+    }
+    const request = new SimLambdaHttpRequest({ target, outbound, scheme });
+    const callback = callArguments.at(-1);
+    if (typeof callback === "function") {
+        request.on("response", callback);
+    }
+    return request;
+}
+//# sourceMappingURL=sim-lambda-http-module.js.map

package/dist/service/lambda/function/outbound/sim-lambda-http-module.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"sim-lambda-http-module.js","sourceRoot":"","sources":["../../../../../src/service/lambda/function/outbound/sim-lambda-http-module.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,oBAAoB,EAAE,MAAM,8BAA8B,CAAC;AACpE,OAAO,EAAE,uBAAuB,EAAE,MAAM,6BAA6B,CAAC;AAQtE;;;;GAIG;AACH,MAAM,iBAAiB,GAAgC,IAAI,GAAG,CAAC;IAC7D,CAAC,MAAM,EAAE,OAAO,CAAC;IACjB,CAAC,WAAW,EAAE,OAAO,CAAC;IACtB,CAAC,OAAO,EAAE,QAAQ,CAAC;IACnB,CAAC,YAAY,EAAE,QAAQ,CAAC;CACzB,CAAC,CAAC;AAEH;;GAEG;AACH,MAAM,UAAU,8BAA8B,CAAC,SAAiB;IAC9D,OAAO,iBAAiB,CAAC,GAAG,CAAC,SAAS,CAAC,CAAC;AAC1C,CAAC;AAED;;;GAGG;AACH,MAAM,UAAU,yBAAyB,CAAC,SAAiB;IACzD,OAAO,iBAAiB,CAAC,GAAG,CAAC,SAAS,CAAC,IAAI,QAAQ,CAAC;AACtD,CAAC;AAeD;;;;;;;;;;;;;;;GAeG;AACH,MAAM,UAAU,uBAAuB,CACrC,UAAyC;IAEzC,MAAM,EAAE,UAAU,EAAE,GAAG,UAAU,CAAC;IAClC,MAAM,WAAW,GAAG,UAAU,CAAC,SAAS,CAAoB,CAAC;IAC7D,MAAM,OAAO,GAAG,UAAU,CAAC,KAAK,CAAoB,CAAC;IAErD,OAAO;QACL,GAAG,UAAU;QACb,OAAO,EAAE,CAAC,GAAG,aAAwB,EAAW,EAAE;YAChD,MAAM,SAAS,GAAG,gBAAgB,CAAC,aAAa,EAAE,UAAU,CAAC,CAAC;YAE9D,OAAO,SAAS,IAAI,WAAW,CAAC,GAAG,aAAa,CAAC,CAAC;QACpD,CAAC;QACD;;;WAGG;QACH,GAAG,EAAE,CAAC,GAAG,aAAwB,EAAW,EAAE;YAC5C,MAAM,SAAS,GAAG,gBAAgB,CAAC,aAAa,EAAE,UAAU,CAAC,CAAC;YAC9D,IAAI,SAAS,KAAK,SAAS,EAAE,CAAC;gBAC5B,OAAO,OAAO,CAAC,GAAG,aAAa,CAAC,CAAC;YACnC,CAAC;YAED,SAAS,CAAC,GAAG,EAAE,CAAC;YAChB,OAAO,SAAS,CAAC;QACnB,CAAC;KACF,CAAC;AACJ,CAAC;AAED;;;;;;;GAOG;AACH,SAAS,gBAAgB,CACvB,aAAiC,EACjC,UAAyC;IAEzC,MAAM,EAAE,QAAQ,EAAE,MAAM,GAAG,QAAQ,EAAE,GAAG,UAAU,CAAC;IACnD,MAAM,MAAM,GAAG,uBAAuB,CAAC,aAAa,CAAC,CAAC;IACtD,IAAI,MAAM,KAAK,SAAS,IAAI,CAAC,QAAQ,CAAC,MAAM,CAAC,MAAM,CAAC,QAAQ,CAAC,EAAE,CAAC;QAC9D,OAAO,SAAS,CAAC;IACnB,CAAC;IAED,MAAM,OAAO,GAAG,IAAI,oBAAoB,CAAC,EAAE,MAAM,EAAE,QAAQ,EAAE,MAAM,EAAE,CAAC,CAAC;IAEvE,MAAM,QAAQ,GAAG,aAAa,CAAC,EAAE,CAAC,CAAC,CAAC,CAAC,CAAC;IACtC,IAAI,OAAO,QAAQ,KAAK,UAAU,EAAE,CAAC;QACnC,OAAO,CAAC,EAAE,CAAC,UAAU,EAAE,QAAuC,CAAC,CAAC;IAClE,CAAC;IAED,OAAO,OAAO,CAAC;AACjB,CAAC"}

package/dist/service/lambda/function/{code/vm/http/sim-lambda-vm-wire-request.d.ts → outbound/sim-lambda-http-request.d.ts}

@@ -1,6 +1,15 @@
 import { Writable } from "node:stream";
-import type { SimSdkWireHandler } from "../../../../../../sdk/wire/sim-sdk-wire.types.js";
-import type { SimLambdaVmHttpTarget } from "./sim-lambda-vm-http-target.js";
+import type { SimLambdaHttpTarget } from "./sim-lambda-http-target.js";
+import type { SimLambdaOutboundHttp } from "./sim-lambda-outbound-http.js";
+interface SimLambdaHttpRequestProperties {
+    readonly target: SimLambdaHttpTarget;
+    readonly outbound: SimLambdaOutboundHttp;
+    /**
+     * The scheme of the transport module the call was made through, which
+     * stands in when the call itself named none.
+     */
+    readonly scheme: string;
+}
 /**
  * The outgoing request object `http.request` hands back, for a request the
  * simulation answers instead of the network.
@@ -12,11 +21,10 @@ import type { SimLambdaVmHttpTarget } from "./sim-lambda-vm-http-target.js";
  * client may reach for do nothing rather than being absent, since there is no
  * socket to time out.
  */
-export declare class SimLambdaVmWireRequest extends Writable {
-    private readonly target;
-    private readonly handler;
+export declare class SimLambdaHttpRequest extends Writable {
+    private readonly properties;
     private readonly chunks;
-    constructor(target: SimLambdaVmHttpTarget, handler: SimSdkWireHandler);
+    constructor(properties: SimLambdaHttpRequestProperties);
     _write(chunk: unknown, _encoding: BufferEncoding, callback: (error?: Error | null) => void): void;
     /**
      * Answer the request once its body is complete.
@@ -33,5 +41,10 @@ export declare class SimLambdaVmWireRequest extends Writable {
     setNoDelay(): this;
     setSocketKeepAlive(): this;
     private answer;
+    /**
+     * The written request, as the request the simulation is asked to answer.
+     */
+    private request;
 }
-//# sourceMappingURL=sim-lambda-vm-wire-request.d.ts.map
+export {};
+//# sourceMappingURL=sim-lambda-http-request.d.ts.map

package/dist/service/lambda/function/outbound/sim-lambda-http-request.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"sim-lambda-http-request.d.ts","sourceRoot":"","sources":["../../../../../src/service/lambda/function/outbound/sim-lambda-http-request.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,QAAQ,EAAE,MAAM,aAAa,CAAC;AAEvC,OAAO,KAAK,EAAE,mBAAmB,EAAE,MAAM,6BAA6B,CAAC;AACvE,OAAO,KAAK,EAAE,qBAAqB,EAAE,MAAM,+BAA+B,CAAC;AAQ3E,UAAU,8BAA8B;IACtC,QAAQ,CAAC,MAAM,EAAE,mBAAmB,CAAC;IACrC,QAAQ,CAAC,QAAQ,EAAE,qBAAqB,CAAC;IAEzC;;;OAGG;IACH,QAAQ,CAAC,MAAM,EAAE,MAAM,CAAC;CACzB;AAED;;;;;;;;;;GAUG;AACH,qBAAa,oBAAqB,SAAQ,QAAQ;IAGpC,OAAO,CAAC,QAAQ,CAAC,UAAU;IAFvC,OAAO,CAAC,QAAQ,CAAC,MAAM,CAAgB;IAEvC,YAA6B,UAAU,EAAE,8BAA8B,EAEtE;IAEQ,MAAM,CACb,KAAK,EAAE,OAAO,EACd,SAAS,EAAE,cAAc,EACzB,QAAQ,EAAE,CAAC,KAAK,CAAC,EAAE,KAAK,GAAG,IAAI,KAAK,IAAI,GACvC,IAAI,CAGN;IAED;;;;;;OAMG;IACM,MAAM,CAAC,QAAQ,EAAE,CAAC,KAAK,CAAC,EAAE,KAAK,GAAG,IAAI,KAAK,IAAI,GAAG,IAAI,CAE9D;IAED;;OAEG;IACH,UAAU,IAAI,IAAI,CAEjB;IAED,UAAU,IAAI,IAAI,CAEjB;IAED,kBAAkB,IAAI,IAAI,CAEzB;YAEa,MAAM;IAapB;;OAEG;IACH,OAAO,CAAC,OAAO;CAahB"}