lambda-live-debugger 0.0.106 → 0.0.108

package/.husky/pre-commit

@@ -0,0 +1 @@
+npm run typecheck && npm run prettier && npm run lint

package/.prettierignore

@@ -0,0 +1,6 @@
+.lldebugger
+dist
+cdk.out
+.serverless
+.aws-sam
+src/extension/aws

package/.prettierrc

@@ -0,0 +1 @@
+{}

package/LICENSE.md

@@ -24,7 +24,7 @@
      thereof.
 
 1.5. “Incompatible With Secondary Licenses”
-     means
+means
 
      a. that the initial Contributor has attached the notice described in
         Exhibit B to the Covered Software; or
@@ -89,7 +89,6 @@
       otherwise, or (b) ownership of more than fifty percent (50%) of the
       outstanding shares or beneficial ownership of such entity.
 
-
 2. License Grants and Conditions
 
 2.1. Grants
@@ -157,7 +156,6 @@
      Sections 3.1, 3.2, 3.3, and 3.4 are conditions of the licenses granted in
      Section 2.1.
 
-
 3. Responsibilities
 
 3.1. Distribution of Source Form
@@ -232,29 +230,29 @@
 5. Termination
 
 5.1. The rights granted under this License will terminate automatically if You
-     fail to comply with any of its terms. However, if You become compliant,
-     then the rights granted under this License from a particular Contributor
-     are reinstated (a) provisionally, unless and until such Contributor
-     explicitly and finally terminates Your grants, and (b) on an ongoing basis,
-     if such Contributor fails to notify You of the non-compliance by some
-     reasonable means prior to 60 days after You have come back into compliance.
-     Moreover, Your grants from a particular Contributor are reinstated on an
-     ongoing basis if such Contributor notifies You of the non-compliance by
-     some reasonable means, this is the first time You have received notice of
-     non-compliance with this License from such Contributor, and You become
-     compliant prior to 30 days after Your receipt of the notice.
+fail to comply with any of its terms. However, if You become compliant,
+then the rights granted under this License from a particular Contributor
+are reinstated (a) provisionally, unless and until such Contributor
+explicitly and finally terminates Your grants, and (b) on an ongoing basis,
+if such Contributor fails to notify You of the non-compliance by some
+reasonable means prior to 60 days after You have come back into compliance.
+Moreover, Your grants from a particular Contributor are reinstated on an
+ongoing basis if such Contributor notifies You of the non-compliance by
+some reasonable means, this is the first time You have received notice of
+non-compliance with this License from such Contributor, and You become
+compliant prior to 30 days after Your receipt of the notice.
 
 5.2. If You initiate litigation against any entity by asserting a patent
-     infringement claim (excluding declaratory judgment actions, counter-claims,
-     and cross-claims) alleging that a Contributor Version directly or
-     indirectly infringes any patent, then the rights granted to You by any and
-     all Contributors for the Covered Software under Section 2.1 of this License
-     shall terminate.
+infringement claim (excluding declaratory judgment actions, counter-claims,
+and cross-claims) alleging that a Contributor Version directly or
+indirectly infringes any patent, then the rights granted to You by any and
+all Contributors for the Covered Software under Section 2.1 of this License
+shall terminate.
 
 5.3. In the event of termination under Sections 5.1 or 5.2 above, all end user
-     license agreements (excluding distributors and resellers) which have been
-     validly granted by You or Your distributors under this License prior to
-     termination shall survive termination.
+license agreements (excluding distributors and resellers) which have been
+validly granted by You or Your distributors under this License prior to
+termination shall survive termination.
 
 6. Disclaimer of Warranty
 
@@ -266,7 +264,7 @@
    Should any Covered Software prove defective in any respect, You (not any
    Contributor) assume the cost of any necessary servicing, repair, or
    correction. This disclaimer of warranty constitutes an essential part of this
-   License. No use of  any Covered Software is authorized under this License
+   License. No use of any Covered Software is authorized under this License
    except under this disclaimer.
 
 7. Limitation of Liability
@@ -301,7 +299,6 @@
    contract shall be construed against the drafter shall not be used to construe
    this License against a Contributor.
 
-
 10. Versions of the License
 
 10.1. New Versions
@@ -327,9 +324,9 @@
       modified license differs from this License).
 
 10.4. Distributing Source Code Form that is Incompatible With Secondary Licenses
-      If You choose to distribute Source Code Form that is Incompatible With
-      Secondary Licenses under the terms of this version of the License, the
-      notice described in Exhibit B of this License must be attached.
+If You choose to distribute Source Code Form that is Incompatible With
+Secondary Licenses under the terms of this version of the License, the
+notice described in Exhibit B of this License must be attached.
 
 Exhibit A - Source Code Form License Notice
 

package/README.md

@@ -2,7 +2,7 @@
 
 ![Logo](logo.png)
 
-Lambda Live Debugger is an indispensable tool for debugging AWS Lambda functions from your computer, even though they are deployed in the cloud. It supports Lambdas written in JavaScript or TypeScript.
+Lambda Live Debugger ([GitHub](https://github.com/ServerlessLife/lambda-live-debugger)) is an indispensable tool for debugging AWS Lambda functions from your computer, even though they are deployed in the cloud. It supports Lambdas written in JavaScript or TypeScript.
 
 This tool offers similar functionality to [SST](https://sst.dev/) and [Serverless Framework v4](https://www.serverless.com/blog/serverless-framework-v4-general-availability), with the addition of an Observability Mode.
 
@@ -19,28 +19,38 @@ It supports the following frameworks:
 
 **This project is in the early alpha stage. Your feedback is incredibly valuable. Please let me know if it works for you or if you encounter any issues. I've tested many scenarios, but people can configure their projects and TypeScript settings in numerous ways. The tool is flexible and can be adjusted to fit your setup in most cases without needing additional features. If you need help, please let me know. Any suggestions for improvements are welcome.**
 
+If the tool is working well for you, please fill out the general [FEEDBACK FORM](https://forms.gle/v6ekZtuB45Rv3EyW9). This helps me understand how extensively the tool has been tested and whether there is a general interest in its further development.
+
+If you've encountered a bug, need help, or would like to request additional features, please create an issue on [GitHub Issue](https://github.com/ServerlessLife/lambda-live-debugger/issues).
+
 Contact me via:
 
+- [Feedback Form](https://forms.gle/v6ekZtuB45Rv3EyW9)
 - [GitHub Issues](https://github.com/ServerlessLife/lambda-live-debugger/issues)
 - [LinkedIn](http://www.linkedin.com/in/marko-serverlesslife)
 
 ## The Problem Statement
 
-Serverless is amazing and solves many issues with traditional systems. However, writing code for Lambda functions can be challenging. The cycle of writing, deploying, running, fixing, and redeploying is time-consuming and tedious. While local testing tools and unit/integration tests exist, they often don't replicate the actual environment closely enough.
+Serverless is amazing and solves many issues with traditional systems. However, writing code for Lambda functions can be challenging. The cycle of writing, deploying, running, fixing, and redeploying is time-consuming and tedious. You could use tools to run Lambda locally or use unit/integration tests; those approaches often don't replicate the actual environment closely enough.
 
 ## How It Works
 
-Lambda Live Debugger connects to your deployed Lambda, routes requests to your computer, and sends responses back to the Lambda. This allows you to debug locally, but the system behaves as if the code is running in the cloud with the same permissions.
+Lambda Live Debugger connects to your deployed Lambda, routes requests to your computer, and sends responses back to the deployed Lambda. This allows you to debug locally, but the system behaves as if the code is running in the cloud with the same permissions.
 
-The tool attaches Lambda Extensions (via a Layer) to intercept and relay calls to AWS IoT, transferring messages between your Lambda and local machine. If the Lambda is written in TypeScript, it's transpiled to JavaScript. The code is executed via Node Worker Thread.
+The tool attaches Lambda Extensions (via a Layer), intercepts, and relays calls to AWS IoT. AWS IoT transfers messages between your Lambda and local machine. If the Lambda is written in TypeScript, it's transpiled to JavaScript. The code is executed via the Node Worker Thread.
 
 ![Architecture](./architecture.drawio.png)
 
+AWS keys generated on the cloud for Lambda are transferred to the local environment, so the code has the same permissions as it would executed on the cloud. There could be a difference in packaging, mainly regarding static files, which are probably in different locations. You can use additional environment variables to adjust the code:
+
+- `IS_LOCAL = true` = Lambda is executed locally
+- `LOCAL_PROJECT_DIR` = directory of the project
+
 ### Infrastructure Changes
 
 Lambda Live Debugger makes the following changes to your AWS infrastructure:
 
-- Adds Lambda Layer
+- Deploys Lambda Layer
 - Attaches the Layer to each Lambda you're debugging
 - Adds a policy to the Lambda Role for AWS IoT access
 
@@ -71,7 +81,7 @@ _(On Linux and Mac: `sudo npm install lambda-live-debugger -g`)_
 or locally
 
 ```
-npm install lambda-live-debugger -g
+npm install lambda-live-debugger
 ```
 
 _(If installed locally, you must prefix all commands with `npx`, if they are not part of `scripts` in `package.json`.)_
@@ -116,7 +126,7 @@ The configuration is saved to `lldebugger.config.ts`.
 
 ## Configuration file lldebugger.config.ts
 
-Example lldebugger.config.ts:
+Example `lldebugger.config.ts`:
 
 ```typescript
 import { type LldConfigTs } from "lambda-live-debugger";
@@ -138,10 +148,12 @@ The setting are the same as for CLI parameters.
 
 ### Custom framework implementation and adjustment
 
+```typescript
 getLambdas: async (foundLambdas) => {
 //you can customize the list of lambdas here or create your own
 //return foundLambdas;
 },
+```
 
 ### Debugging
 
@@ -209,18 +221,19 @@ I am not a Terraform developer, so I only know the basics. Please provide a samp
 
 ## Know issues
 
-...
+Check the [GitHub issues](https://github.com/ServerlessLife/lambda-live-debugger/issues).
 
 ## Missing Features
 
-Check the [open issues](https://github.com/ServerlessLife/lambda-live-debugger/issues). The biggest missing feature right now is MFA authentication and more Terraform configurations.
+Check the [GitHub issues](https://github.com/ServerlessLife/lambda-live-debugger/issues). The biggest missing feature right now is MFA authentication and more Terraform configurations.
 
 ## Reporting an Issue
 
-- Make sure the bug hasn't already been reported. Add a "+1" comment so I know there are multiple users struggling with the same issue. If possible, add some additional info.
-- Use descriptive titles with prefixes like "bug:", "help:", "feature:", or "discussion:". Please also add the matching label and, if needed, set priority via a label.
+- Make sure the bug hasn't already been reported. If you fount if, add a "+1" comment so I know there are multiple users struggling with the same issue. If possible, add some additional info.
+- Use descriptive titles with prefixes like "bug:", "help:", "feature:", or "discussion:".
 - Enable verbose logging and provide the full log.
 - Describe your setup in detail, or better yet, provide a sample project.
+- Specify exact framework version (CDK, SLS, SAM ...) and exact version of Lambda Live Debugger version.
 
 ## Authors:
 
@@ -229,7 +242,7 @@ Check the [open issues](https://github.com/ServerlessLife/lambda-live-debugger/i
 
 ## Contributors (alphabetical)
 
-- ⭐ Your name here for smaller code/documentation contributions or sample projects as part of bug reports
+- ⭐ Your name here for documentation contributions, minor code additions, or sample projects submitted with bug reports.
 
 ## Declarment
 

package/dist/cloudFormation.mjs

@@ -76,12 +76,12 @@ async function getCloudFormationResources(stackName, awsConfiguration) {
 async function getLambdasInStack(stackName, awsConfiguration) {
     const response = await getCloudFormationResources(stackName, awsConfiguration);
     const lambdaResources = response.StackResourceSummaries?.filter((resource) => resource.ResourceType === "AWS::Lambda::Function");
-    return lambdaResources?.map((resource) => {
+    return (lambdaResources?.map((resource) => {
         return {
             lambdaName: resource.PhysicalResourceId,
             logicalId: resource.LogicalResourceId,
         };
-    });
+    }) ?? []);
 }
 export const CloudFormation = {
     getCloudFormationStackTemplate,

package/dist/configuration/getConfigFromCliArgs.mjs

@@ -11,10 +11,7 @@ export async function getConfigFromCliArgs(supportedFrameworks = []) {
     const version = await getVersion();
     const program = new Command();
     program.name("lld").description("Lambda Live Debugger").version(version);
-    program.option("-r, --remove [option]", "Remove Lambda Live Debugger infrastructure. Options: 'keep-layer' (default), 'remove-all'. The latest also removes the Lambda Layer"
-    //validateRemoveOption,
-    //"keep-layer"
-    );
+    program.option("-r, --remove [option]", "Remove Lambda Live Debugger infrastructure. Options: 'keep-layer' (default), 'remove-all'. The latest also removes the Lambda Layer");
     program.option("-w, --wizard", "Program interactively asks for each parameter and saves it to lldebugger.config.ts");
     program.option("-v, --verbose", "Verbose logs");
     program.option("-c, --context <context>", "AWS CDK context", (value, previous) => previous.concat(value), []);

package/dist/configuration/getConfigFromTsConfigFile.mjs

@@ -14,7 +14,7 @@ export async function getConfigTsFromConfigFile(configFile) {
     try {
         await fs.stat(configFile);
     }
-    catch (err) {
+    catch {
         return undefined;
     }
     try {

package/dist/configuration/getConfigFromWizard.mjs

@@ -89,7 +89,6 @@ export async function getConfigFromWizard({ configFromCliArgs, supportedFramewor
         ]);
         answers = { ...answers, ...samAnswers };
     }
-    answers.framework === currentFramework ? undefined : answers.framework;
     // monorepo subfolder
     const answersSubfolder = await inquirer.prompt([
         {

package/dist/extension/nodejs/node_modules/interceptor.js

@@ -49727,57 +49727,62 @@ async function handler(event, context) {
   }
 }
 async function regularMode(context, event) {
-  return new Promise(async (resolve, reject) => {
-    const timeout = setTimeout(() => {
-      resolve({
-        statusCode: 500,
-        body: "The function's in live debug mode but it hasn't heard back from your machine yet. If this is the first time you're trying out Lambda Live Debugger on this AWS account, AWS might need around 10 minutes to get everything ready. Hang tight and check back in a bit!"
-      });
-    }, 5 * 1e3);
-    const ioTService = await IoTService.connect({
-      onMessage: async (message) => {
-        Logger.log("IoT message", message);
-        if (message.type === "PING") {
-          if (message.data.workerId === workerId) {
-            Logger.log("Pinged by the debugger");
-            clearTimeout(timeout);
-          }
-        }
-        if (["SUCCESS", "ERROR"].includes(message.type)) {
-          if (message.data.workerId === workerId) {
-            clearTimeout(timeout);
-          }
-        }
-        if (message.type === "SUCCESS") {
-          resolve(message.data.body);
+  let promiseResolve;
+  let promiseReject;
+  const promise = new Promise((resolve, reject) => {
+    promiseResolve = resolve;
+    promiseReject = reject;
+  });
+  const timeout = setTimeout(() => {
+    promiseResolve({
+      statusCode: 500,
+      body: "The function's in live debug mode but it hasn't heard back from your machine yet. If this is the first time you're trying out Lambda Live Debugger on this AWS account, AWS might need around 10 minutes to get everything ready. Hang tight and check back in a bit!"
+    });
+  }, 5 * 1e3);
+  const ioTService = await IoTService.connect({
+    onMessage: async (message) => {
+      Logger.log("IoT message", message);
+      if (message.type === "PING") {
+        if (message.data.workerId === workerId) {
+          Logger.log("Pinged by the debugger");
+          clearTimeout(timeout);
         }
-        if (message.type === "ERROR") {
-          const error = new Error(message.data.errorMessage);
-          error.stack = message.data.trace;
-          reject(error);
+      }
+      if (["SUCCESS", "ERROR"].includes(message.type)) {
+        if (message.data.workerId === workerId) {
+          clearTimeout(timeout);
         }
-      },
-      topic
-    });
-    const payload = {
-      type: "INVOKE",
-      data: {
-        workerId,
-        requestId: context.awsRequestId,
-        functionId: process.env.LLD_FUNCTION_ID,
-        deadline: context.getRemainingTimeInMillis(),
-        event,
-        context,
-        env: process.env
       }
-    };
-    Logger.log(
-      "Publishing to IoT",
-      `${process.env.LLD_DEBUGGER_ID}/events`,
-      payload
-    );
-    await ioTService.publish(payload, `${process.env.LLD_DEBUGGER_ID}/events`);
+      if (message.type === "SUCCESS") {
+        promiseResolve(message.data.body);
+      }
+      if (message.type === "ERROR") {
+        const error = new Error(message.data.errorMessage);
+        error.stack = message.data.trace;
+        promiseReject(error);
+      }
+    },
+    topic
   });
+  const payload = {
+    type: "INVOKE",
+    data: {
+      workerId,
+      requestId: context.awsRequestId,
+      functionId: process.env.LLD_FUNCTION_ID,
+      deadline: context.getRemainingTimeInMillis(),
+      event,
+      context,
+      env: process.env
+    }
+  };
+  Logger.log(
+    "Publishing to IoT",
+    `${process.env.LLD_DEBUGGER_ID}/events`,
+    payload
+  );
+  await ioTService.publish(payload, `${process.env.LLD_DEBUGGER_ID}/events`);
+  return promise;
 }
 async function observableMode(context, event) {
   const regularHandler = async () => {