@kensio/yulin 1.14.0 → 1.14.1

package/dist/service/lambda/function/code/vm/sim-lambda-vm-context.d.ts

@@ -6,7 +6,8 @@ import type { SimLambdaEnvironment } from "../../environment/sim-lambda-environm
  *
  * The context provides the common globals a Node.js Lambda runtime offers,
  * including an AWS-like process.env holding the standard runtime variables
- * and any variables declared for the function. Everything else must be part
+ * and any variables declared for the function, and the writable standard
+ * streams function code writes its output to. Everything else must be part
  * of the deployed function code archive, as on real Lambda.
  *
  * Zip code needs nothing like the process.env and Date handling the

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

@@ -1 +1 @@
-{"version":3,"file":"sim-lambda-vm-context.d.ts","sourceRoot":"","sources":["../../../../../../src/service/lambda/function/code/vm/sim-lambda-vm-context.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,MAAM,SAAS,CAAC;AAEzB,OAAO,EACL,KAAK,QAAQ,EAEd,MAAM,wCAAwC,CAAC;AAChD,OAAO,KAAK,EAAE,oBAAoB,EAAE,MAAM,6CAA6C,CAAC;AAExF;;;;;;;;;;;;GAYG;AACH,wBAAgB,sBAAsB,CACpC,WAAW,EAAE,oBAAoB,EACjC,KAAK,GAAE,QAA6B,GACnC,EAAE,CAAC,OAAO,CAuBZ"}
+{"version":3,"file":"sim-lambda-vm-context.d.ts","sourceRoot":"","sources":["../../../../../../src/service/lambda/function/code/vm/sim-lambda-vm-context.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,MAAM,SAAS,CAAC;AAEzB,OAAO,EACL,KAAK,QAAQ,EAEd,MAAM,wCAAwC,CAAC;AAChD,OAAO,KAAK,EAAE,oBAAoB,EAAE,MAAM,6CAA6C,CAAC;AAGxF;;;;;;;;;;;;;GAaG;AACH,wBAAgB,sBAAsB,CACpC,WAAW,EAAE,oBAAoB,EACjC,KAAK,GAAE,QAA6B,GACnC,EAAE,CAAC,OAAO,CAkCZ"}

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

@@ -1,12 +1,15 @@
+import { Console } from "node:console";
 import vm from "node:vm";
 import { makeSimClockDate } from "../../../../../util/clock/sim-clock-date.js";
 import { SimRealClock, } from "../../../../../util/clock/sim-clock.js";
+import { SimLambdaVmOutputStream } from "./sim-lambda-vm-output-stream.js";
 /**
  * Create the sandbox vm context that sim Lambda function code runs in.
  *
  * The context provides the common globals a Node.js Lambda runtime offers,
  * including an AWS-like process.env holding the standard runtime variables
- * and any variables declared for the function. Everything else must be part
+ * and any variables declared for the function, and the writable standard
+ * streams function code writes its output to. Everything else must be part
  * of the deployed function code archive, as on real Lambda.
  *
  * Zip code needs nothing like the process.env and Date handling the
@@ -15,11 +18,21 @@ import { SimRealClock, } from "../../../../../util/clock/sim-clock.js";
  * nothing outside the sandbox is touched to arrange that.
  */
 export function makeSimLambdaVmContext(environment, clock = new SimRealClock()) {
+    // Writable standard streams, as the real runtime provides. Code that builds
+    // its own console over them, as AWS Lambda Powertools' logger does, throws
+    // at module load without them.
+    const stdout = new SimLambdaVmOutputStream(() => process.stdout);
+    const stderr = new SimLambdaVmOutputStream(() => process.stderr);
     return vm.createContext({
-        console,
+        // The sandbox's console is built over those streams, as the real
+        // runtime's is, so everything function code prints goes to one place
+        // whether it printed through the console or wrote to the stream itself.
+        console: new Console({ stdout, stderr }),
         Buffer,
         process: {
             env: environment.variables(),
+            stdout,
+            stderr,
         },
         // Function code asking JavaScript for the time gets the simulation's
         // time, so a frozen or advanced clock reaches the code under test.

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,MAAM,SAAS,CAAC;AACzB,OAAO,EAAE,gBAAgB,EAAE,MAAM,6CAA6C,CAAC;AAC/E,OAAO,EAEL,YAAY,GACb,MAAM,wCAAwC,CAAC;AAGhD;;;;;;;;;;;;GAYG;AACH,MAAM,UAAU,sBAAsB,CACpC,WAAiC,EACjC,KAAK,GAAa,IAAI,YAAY,EAAE;IAEpC,OAAO,EAAE,CAAC,aAAa,CAAC;QACtB,OAAO;QACP,MAAM;QACN,OAAO,EAAE;YACP,GAAG,EAAE,WAAW,CAAC,SAAS,EAAE;SAC7B;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,EAAE,uBAAuB,EAAE,MAAM,kCAAkC,CAAC;AAE3E;;;;;;;;;;;;;GAaG;AACH,MAAM,UAAU,sBAAsB,CACpC,WAAiC,EACjC,KAAK,GAAa,IAAI,YAAY,EAAE;IAEpC,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,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"}

package/dist/service/lambda/function/code/vm/sim-lambda-vm-output-stream.d.ts

@@ -0,0 +1,40 @@
+import { Writable } from "node:stream";
+/**
+ * One of the standard output streams the sim Lambda vm sandbox gives function
+ * code as `process.stdout` and `process.stderr`.
+ *
+ * Real Lambda gives function code writable standard streams, and libraries
+ * build their own console over them rather than the global one, so that
+ * console patching cannot affect their output. AWS Lambda Powertools' logger
+ * does exactly that, at module scope:
+ *
+ * ```javascript
+ * new Console({ stdout: process.stdout, stderr: process.stderr })
+ * ```
+ *
+ * Without the streams that construction throws
+ * (`ERR_CONSOLE_WRITABLE_STREAM`) before the handler runs.
+ *
+ * What function code writes is forwarded to the matching host stream,
+ * standard output to standard output and standard error to standard error.
+ * The sandbox's own console is built over these streams too, so a handler's
+ * output arrives there whether it printed through the console or wrote to the
+ * stream itself, instead of one of the two disappearing. The host stream is
+ * read per write, so a test that starts capturing host output after the
+ * function has cold-started still sees what the handler writes.
+ */
+export declare class SimLambdaVmOutputStream extends Writable {
+    private readonly hostStream;
+    constructor(hostStream: () => NodeJS.WritableStream);
+    /**
+     * The write is handed on and reported as done without waiting for the host
+     * stream, as Node.js's own console hands writes to process.stdout. Waiting
+     * would make a failed log write fail the code that logged: reporting the
+     * host's error here destroys this stream, and with nothing listening for
+     * its error the process goes down over a lost line. It would also mean a
+     * test capturing host output had to complete the write it captured, and the
+     * ordinary way to capture it does not.
+     */
+    _write(chunk: Buffer, _encoding: BufferEncoding, done: (error?: Error) => void): void;
+}
+//# sourceMappingURL=sim-lambda-vm-output-stream.d.ts.map

package/dist/service/lambda/function/code/vm/sim-lambda-vm-output-stream.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"sim-lambda-vm-output-stream.d.ts","sourceRoot":"","sources":["../../../../../../src/service/lambda/function/code/vm/sim-lambda-vm-output-stream.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,QAAQ,EAAE,MAAM,aAAa,CAAC;AAEvC;;;;;;;;;;;;;;;;;;;;;;;GAuBG;AACH,qBAAa,uBAAwB,SAAQ,QAAQ;IACvC,OAAO,CAAC,QAAQ,CAAC,UAAU;IAAvC,YAA6B,UAAU,EAAE,MAAM,MAAM,CAAC,cAAc,EAEnE;IAED;;;;;;;;OAQG;IACM,MAAM,CACb,KAAK,EAAE,MAAM,EACb,SAAS,EAAE,cAAc,EACzB,IAAI,EAAE,CAAC,KAAK,CAAC,EAAE,KAAK,KAAK,IAAI,GAC5B,IAAI,CAGN;CACF"}

package/dist/service/lambda/function/code/vm/sim-lambda-vm-output-stream.js

@@ -0,0 +1,46 @@
+import { Writable } from "node:stream";
+/**
+ * One of the standard output streams the sim Lambda vm sandbox gives function
+ * code as `process.stdout` and `process.stderr`.
+ *
+ * Real Lambda gives function code writable standard streams, and libraries
+ * build their own console over them rather than the global one, so that
+ * console patching cannot affect their output. AWS Lambda Powertools' logger
+ * does exactly that, at module scope:
+ *
+ * ```javascript
+ * new Console({ stdout: process.stdout, stderr: process.stderr })
+ * ```
+ *
+ * Without the streams that construction throws
+ * (`ERR_CONSOLE_WRITABLE_STREAM`) before the handler runs.
+ *
+ * What function code writes is forwarded to the matching host stream,
+ * standard output to standard output and standard error to standard error.
+ * The sandbox's own console is built over these streams too, so a handler's
+ * output arrives there whether it printed through the console or wrote to the
+ * stream itself, instead of one of the two disappearing. The host stream is
+ * read per write, so a test that starts capturing host output after the
+ * function has cold-started still sees what the handler writes.
+ */
+export class SimLambdaVmOutputStream extends Writable {
+    hostStream;
+    constructor(hostStream) {
+        super();
+        this.hostStream = hostStream;
+    }
+    /**
+     * The write is handed on and reported as done without waiting for the host
+     * stream, as Node.js's own console hands writes to process.stdout. Waiting
+     * would make a failed log write fail the code that logged: reporting the
+     * host's error here destroys this stream, and with nothing listening for
+     * its error the process goes down over a lost line. It would also mean a
+     * test capturing host output had to complete the write it captured, and the
+     * ordinary way to capture it does not.
+     */
+    _write(chunk, _encoding, done) {
+        this.hostStream().write(chunk);
+        done();
+    }
+}
+//# sourceMappingURL=sim-lambda-vm-output-stream.js.map

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

@@ -0,0 +1 @@
+{"version":3,"file":"sim-lambda-vm-output-stream.js","sourceRoot":"","sources":["../../../../../../src/service/lambda/function/code/vm/sim-lambda-vm-output-stream.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,QAAQ,EAAE,MAAM,aAAa,CAAC;AAEvC;;;;;;;;;;;;;;;;;;;;;;;GAuBG;AACH,MAAM,OAAO,uBAAwB,SAAQ,QAAQ;IACtB,UAAU;IAAvC,YAA6B,UAAuC;QAClE,KAAK,EAAE,CAAC;0BADmB,UAAU;IAEvC,CAAC;IAED;;;;;;;;OAQG;IACM,MAAM,CACb,KAAa,EACb,SAAyB,EACzB,IAA6B;QAE7B,IAAI,CAAC,UAAU,EAAE,CAAC,KAAK,CAAC,KAAK,CAAC,CAAC;QAC/B,IAAI,EAAE,CAAC;IACT,CAAC;CACF"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@kensio/yulin",
-  "version": "1.14.0",
+  "version": "1.14.1",
   "description": "AWS system behaviour simulation for isolated unit testing",
   "repository": "https://github.com/KensioSoftware/yulin",
   "homepage": "https://yulinsim.dev/",
@@ -163,6 +163,8 @@
   "packageManager": "pnpm@11.17.0+sha512.cca3cea332ad254bb84145f966d19f4879615210346fc92c79a047f23a0d7b3cca3c3792f0076ba1f1831d277efbcf0a9119b31a9a60eca7fb3d6231f331ef72",
   "devDependencies": {
     "@aws-crypto/sha256-js": "^5.2.0",
+    "@aws-lambda-powertools/logger": "^2.34.0",
+    "@aws-lambda-powertools/metrics": "^2.34.0",
     "@aws-sdk/client-acm": "^3.1101.0",
     "@aws-sdk/client-apigatewayv2": "^3.1101.0",
     "@aws-sdk/client-cloudformation": "^3.1101.0",
@@ -204,6 +206,7 @@
     "aws-sdk-client-mock": "^4.1.0",
     "constructs": "^10.8.0",
     "conventional-changelog-conventionalcommits": "9.3.1",
+    "esbuild": "^0.28.2",
     "eslint": "^10.8.0",
     "eslint-plugin-jsdoc": "^63.3.2",
     "eslint-plugin-no-secrets": "^2.3.3",