cat-a-logs 2.0.0 → 2.0.2

package/README.md

@@ -1,47 +1,55 @@
-# cat-a-log
-This function will help you create AWS Embedded Metric Format Logs and publish them to AWS Cloudwatch. EMF formatting will allow for chosen metrics to be automatically visualized in graphs for simplier debugging.
+# Welcome to Cat-A-Log!
+This npm package will help you create AWS Embedded Metric Format Logs and publish them to AWS Cloudwatch using AWS Lambda Powertools. EMF formatting will allow for chosen metrics to be automatically visualized in Cloudwatch metrics  for simplier log debugging.
 
-**What is Embedded Metric Formatting (EMF):**\
-This is a JSON specification to communicate with Cloudwatch Logs to automatically extract values embedded in the structured log events.
-EMF is especially great for applications that make logs and need custom metrics without more complexity or cost.
- For more information please visit the link below 
+  <p align="center">
+  <img src="./snapshots/Catalog_art.png" width="200" />
+  </p>
 
+
+## About Embedded Metric Formatting (EMF):
+This is a JSON specification to communicate with Cloudwatch Logs to automatically extract values embedded in the structured log events. EMF is especially great for applications that make logs and need custom metrics without more complexity or cost. For more information please visit the following link:
 <a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch_Embedded_Metric_Format_Specification.html" target="_blank">AWS Documentation on EMF Formatting</a>
 
+## Why use Cat-A-Log?
+Why use a washing machine when you can do them by hand? Because it saves you time and makes your job way easier! Leveraging AWS Lambda Powertools we can use the cat-a-log function to invoke and format logs into AWS Embedded Metric Format. By publishing these logs to AWS Cloudwatch, we are able to provide engineers with automatic metric visulaization to make the process of debugging logs much more efficient. Cat-a-log utilizies a cache to make effcient work of sending logs to Cloudwatch.
+
+
+## Instructions
+**Prerequites:**
+Your chosen Integated Development Environment (i.e. VS Code) must already be be connected to AWS Lambda. For more guidence on setting up AWS Lambda we recommend following this helpful tutorial from AWS: <a href="https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/serverless-getting-started-hello-world.html" target="_blank">Deploy Hello World Application with AWS SAM</a>
 
-**Why use cat-a-log?:**\
-Why use a washing machine when you can do them by hand? Becuase it makes your job way easier! Leveraging AWS Lambda Powertools we can use the cat-a-log function to invoke and format logs into AWS Embedded Metric Format. By publishing these logs to AWS Cloudwatch, we are able to provide engineers with automatic metric visulaization to make the process of debugging logs much more efficient. Cat-a-log utilizies a cache to make effcient work of sending logs to Cloudwatch.
+**Installation:**
+1. Install our package using the command `npm install cat-a-logs` then import the function and cache into your js file that connects to AWS Lambda `import { cache, catalog } from "cat-a-logs/index.js";` Check out Cat-A-Log on npm using the attached link:
+<a href="https://www.npmjs.com/package/cat-a-logs?activeTab=readme" target="_blank">Cat-A-Log</a>
 
+2. Now enter your arguments into the catalog function! Lets go through each argument one at a time and see what this looks like. First Lets take a look at the function definition:
 
-**How do I use cat-a-log?:**\
-npm install  our package using the command `npm install cat-a-logs` into your app.mjs file then capture the function and cache (we will talk about this later) 
-`import {cache, catalog} from "cat-a-logs/index.js";`
+      ```
+      function catalog(
+        trackedVariable: number | Array<number>,
+        metricName: string,
+        metricNamespace: string,
+        metricUnitLabel: string = "None",
+        CustomerDefinedDimension: { [key: string]: string } = {},
+        resolution: 1 | 60 = 60,
+        deploy: boolean = false)
+      ```
 
-The catalog function  below takes in the following arguments - lets look at each argument one at a time:
+    - **trackedVariable**: This variable represents a number that is dynamic and can change with each call - these numbers are reflected under Metrics
+    - **metricName**: This is a unique label of the tracked variable that will be reflected inside AWS Lambda. Must be written as a `string`
+    - **metricNamespace**: This will be your metric namespace in AWS Cloudwatch the metric or metrics will appear in
+    - **metricUnitLabel**: Explict Unit that Cloudwatch uses for EMF Configuration. Please note - Can only be the following labels:
+      - Seconds | Microseconds | Milliseconds | Bytes | Kilobytes | Megabytes | Gigabytes | Terabytes | Bits | Kilobits | Megabits | Gigabits | Terabits | Percent | Count | Bytes/Second | Kilobytes/Second | Megabytes/Second | Gigabytes/Second | Terabytes/Second | Bits/Second | Kilobits/Second | Megabits/Second | Gigabits/Second | Terabits/Second | Count/Second | None
 
-`function catalog(
-  trackedVariable: number | Array<number>,
-  metricName: string,
-  metricNamespace: string,
-  metricUnitLabel: string = "None",
-  CustomerDefinedDimension: { [key: string]: string } = {},
-  resolution: 1 | 60 = 60,
-  deploy: boolean = false
-)`
+      - To read more about Metric Datum see this <a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/APIReference/API_MetricDatum.html" target="_blank">link</a>
+    - **CustomerDefinedDimension**: This is an object - key will be demension and value 
+    - **resolution**: automatically set to default value
+    - **deploy**: automatically set to false 
 
-- **trackedVariable**: This is a number that is dynamic and can change with each call - these numbers are reflected 
-- **metricName**:
-- **metricNamespace**:
-- **metricUnitLabel**: Can only be the following labels:
-- Seconds | Microseconds | Milliseconds | Bytes | Kilobytes | Megabytes | Gigabytes | Terabytes | Bits | Kilobits | Megabits | Gigabits | Terabits | Percent | Count | Bytes/Second | Kilobytes/Second | Megabytes/Second | Gigabytes/Second | Terabytes/Second | Bits/Second | Kilobits/Second | Megabits/Second | Gigabits/Second | Terabits/Second | Count/Second | None\
 
-To read more about Metric Datum see this <a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/APIReference/API_MetricDatum.html" target="_blank">link</a>
-- **CustomerDefinedDimension**: 
-- **resolution**: 
-- **deploy**: 
 
-**Structure of the files:**\
-<a href="https://www.npmjs.com/package/cat-a-logs?activeTab=readme" target="_blank">Link to npm package</a>
+## Notes to Self:
+**Structure of the files:**
 
 `index.ts` is compiled to `index.js`. Important to compile `.ts` file to es6 js syntax using the `tsc —target es6 (filepath)` command
 `app.mjs ` is a "pathway" to our lambda function. Here is where we will import catalog function and use it to involke our lambda function
@@ -54,4 +62,57 @@ logger.info gives you some information level is key and value is info
 if you write name that it will overwrite the keys 
 
 **Tech Challenges**
-Spent 3 days dealing with inconsistencies of ES6/CommonJS in our code before compiling .js in ES6
+Spent 3 days dealing with inconsistencies of ES6/CommonJS in our code before compiling .js in ES6
+
+**Files to Delete**
+App.js
+App.tsx
+tailwind.css?
+tailwind.config.js
+input.css?
+postcss.config.js
+server(folder)
+coverage (folder)
+bin (folder)
+template.html
+testlogger.js 
+
+-->webpack.config.js?  **Test renaming to see if it breaks.  
+
+Package json: 
+    "@babel/core": "^7.25.7",
+    "@babel/plugin-transform-runtime": "^7.25.7",
+    "@babel/preset-env": "^7.25.8",
+    "@babel/preset-react": "^7.25.7",
+    "@babel/runtime": "^7.25.7",
+    "babel-eslint": "^10.1.0",
+    "babel-loader": "^9.2.1",
+    "cross-env": "^7.0.3",
+    "css-loader": "^7.1.2",
+    "html-webpack-plugin": "^5.6.0",
+    "node-mocks-http": "^1.16.1",
+    "nodemon": "^3.1.7",
+    "postcss": "^8.4.49",
+    "postcss-loader": "^8.1.1",
+    "postcss-preset-env": "^10.1.1",
+    "sass": "^1.80.5",
+    "sass-loader": "^16.0.2",
+    "style-loader": "^4.0.0",
+    "tailwindcss": "^3.4.15",
+    "webpack": "^5.95.0",
+    "webpack-cli": "^5.1.4",
+    "webpack-dev-server": "^5.1.0"
+    "bcrypt": "^5.1.1",
+    "cookie-parser": "^1.4.7",
+    "cors": "^2.8.5",
+    "express": "^4.21.1",
+    "express-session": "^1.18.1",
+    "react": "^18.3.1",
+    "react-dom": "^18.3.1",
+    "react-router-dom": "^6.27.0"
+
+**npmignore**
+lambda-nodejs22.x
+
+**gitignore**
+lambda-nodejs22.x

package/client/index.ts

@@ -204,9 +204,7 @@ async function catalog(
     // validate the new EMF JSON schema against AWS EMF JSON schema before adding to cache object
     const isValid = validateEmf(newEmfLog);
     // //troubleshooting console.error in test
-    // console.log('index.ts - Validation result: ', isValid);
     // troubleshooting console.error in emf test
-    // console.log('index.ts - Validation errors: ', validateEmf.errors);
     // if it fails validation throw error
     if (!isValid) {
       console.error(
@@ -236,56 +234,3 @@ async function catalog(
   }
 }
 export { cache, catalog };
-
-/*Current Working logger invocation
-logger.info("Your EMF compliant Structured Metrics Log",
-  Object.assign({
-    _aws: {
-      Timestamp: Date.now(),
-      CloudWatchMetrics: [
-        {
-          Namespace: metricNamespace,
-          Dimensions: [Object.keys(CustomerDefinedDimension)],
-          Metrics: [
-            {
-              Name: metricName,
-              Unit: metricUnitLabel,
-              StorageResolution: resolution,
-            }
-          ]
-        }
-      ]
-    },
-    [`${metricName}`]: trackedVariable,
-    }, 
-      CustomerDefinedDimension
-    )
-  
-)
-*/
-
-//Old handler function
-// export const handler = async (_event, _context): Promise<void> => {
-//   const testObj = {
-//     testguy: "hi",
-//     fool: 42,
-//     functionVersion: "$LATEST",
-//     _aws: {
-//       Timestamp: Date.now(),
-//       CloudWatchMetrics: [
-//         {
-//           Namespace: "lambda-function-metrics",
-//           Dimensions: [["functionVersion"]],
-//           Metrics: [
-//             {
-//               Name: "fool",
-//               Unit: "Milliseconds",
-//               StorageResolution: 60
-//             }
-//           ]
-//         }
-//       ]
-//     },
-//   }
-//   logger.info(JSON.stringify(testObj));
-// };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "cat-a-logs",
-  "version": "2.0.0",
+  "version": "2.0.2",
   "description": "Create & send structured logs to AWS Cloudwatch logs",
   "main": "index.js",
   "exports":{
@@ -17,34 +17,13 @@
   "license": "ISC",
   "type": "module",
   "devDependencies": {
-    "@babel/core": "^7.25.7",
-    "@babel/plugin-transform-runtime": "^7.25.7",
-    "@babel/preset-env": "^7.25.8",
-    "@babel/preset-react": "^7.25.7",
-    "@babel/runtime": "^7.25.7",
-    "@types/jest": "^29.5.14",
-    "babel-eslint": "^10.1.0",
-    "babel-loader": "^9.2.1",
-    "concurrently": "^9.0.1",
-    "cross-env": "^7.0.3",
-    "css-loader": "^7.1.2",
-    "html-webpack-plugin": "^5.6.0",
-    "jest": "^29.7.0",
-    "node-mocks-http": "^1.16.1",
-    "nodemon": "^3.1.7",
-    "postcss": "^8.4.49",
-    "postcss-loader": "^8.1.1",
-    "postcss-preset-env": "^10.1.1",
-    "sass": "^1.80.5",
-    "sass-loader": "^16.0.2",
-    "style-loader": "^4.0.0",
-    "tailwindcss": "^3.4.15",
     "ts-jest": "^29.2.5",
     "ts-loader": "^9.5.1",
     "typescript": "^5.7.3",
-    "webpack": "^5.95.0",
-    "webpack-cli": "^5.1.4",
-    "webpack-dev-server": "^5.1.0"
+    "jest": "^29.7.0",
+    "@types/jest": "^29.5.14",
+    "concurrently": "^9.0.1",
+    "cross-env": "^7.0.3"
   },
   "dependencies": {
     "@aws-lambda-powertools/logger": "^2.11.0",
@@ -54,16 +33,8 @@
     "@testing-library/react": "^16.0.1",
     "@testing-library/user-event": "^14.5.2",
     "ajv": "^8.17.1",
-    "bcrypt": "^5.1.1",
-    "cookie-parser": "^1.4.7",
-    "cors": "^2.8.5",
-    "dotenv": "^16.4.7",
-    "express": "^4.21.1",
-    "express-session": "^1.18.1",
     "jest-environment-jsdom": "^29.7.0",
     "lambda-log": "^3.1.0",
-    "react": "^18.3.1",
-    "react-dom": "^18.3.1",
-    "react-router-dom": "^6.27.0"
+    "dotenv": "^16.4.7"
   }
 }

package/.babelrc

@@ -1,13 +0,0 @@
-{
-    "presets": [
-      "@babel/preset-env",
-      [
-        "@babel/preset-react",
-        {
-          "runtime": "automatic" // allows use of JSX w/out import React from "react" in every component file - BMA
-        }
-      ]
-    ],
-    "plugins": ["@babel/plugin-transform-runtime"]
-  }
-  

package/bin/catalogExe.js

@@ -1,4 +0,0 @@
-#!/usr/bin/env node;  
-//Above (UNIX - shebang) used to indicate this is an executable file that will use node as its interpreter
-
-

package/client/App.js

@@ -1 +0,0 @@
-"use strict";

package/client/css/input.css

@@ -1,3 +0,0 @@
-/* @tailwind base;
-@tailwind components;
-@tailwind utilities; */

package/client/template.html

@@ -1,18 +0,0 @@
-<!-- Used by HTMLWebpackPlugin (per plugins config in webpack.config.js)
-  to build index.html with each webpack rebuild/rebundle -->
-
-  <!DOCTYPE html>
-  <html>
-    <head>
-      <meta charset="utf-8" />
-      <meta http-equiv="X-UA-Compatible" content="IE=edge" />
-      <title>%= htmlWebpackPlugin.options.title %</title>
-      <meta name="viewport" content="width=device-width, initial-scale=1" />
-    </head>
-    <body>
-        <h1 class="text-4xl text-blue-700">My Webpack + Tailwind App</h1>
-        <script src="dist/bundle.js"></script>
-      <!-- Insert React App here -->
-      <div id="root"></div>
-    </body>
-  </html>

package/lambda-nodejs22.x/README.TOOLKIT.md

@@ -1,38 +0,0 @@
-# Developing AWS SAM Applications with the AWS Toolkit For Visual Studio Code
-
-This project contains source code and supporting files for a serverless application that you can locally run, debug, and deploy to AWS with the AWS Toolkit For Visual Studio Code.
-
-A "SAM" (serverless application model) project is a project that contains a template.yaml file which is understood by AWS tooling (such as SAM CLI, and the AWS Toolkit For Visual Studio Code).
-
-## Writing and Debugging Serverless Applications
-
-The code for this application will differ based on the runtime, but the path to a handler can be found in the [`template.yaml`](./template.yaml) file through a resource's `CodeUri` and `Handler` fields.
-
-AWS Toolkit For Visual Studio Code supports local debugging for serverless applications through VS Code's debugger. Since this application was created by the AWS Toolkit, launch configurations for all included handlers have been generated and can be found in the menu next to the Run button:
-
-* lambda-nodejs22.x:HelloWorldFunction (nodejs22.x)
-* API lambda-nodejs22.x:HelloWorldFunction (nodejs22.x)
-
-You can debug the Lambda handlers locally by adding a breakpoint to the source file, then running the launch configuration. This works by using Docker on your local machine.
-
-Invocation parameters, including payloads and request parameters, can be edited either by the `Local Invoke and Debug Configuration` command (through the Command Palette or CodeLens) or by editing the `launch.json` file.
-
-AWS Lambda functions not defined in the [`template.yaml`](./template.yaml) file can be invoked and debugged by creating a launch configuration through the CodeLens over the function declaration, or with the `Add Local Invoke and Debug Configuration` command.
-
-## Deploying Serverless Applications
-
-You can deploy a serverless application by invoking the `AWS: Deploy SAM application` command through the Command Palette or by right-clicking the Lambda node in the AWS Explorer and entering the deployment region, a valid S3 bucket from the region, and the name of a CloudFormation stack to deploy to. You can monitor your deployment's progress through the `AWS Toolkit` Output Channel.
-
-## Interacting With Deployed Serverless Applications
-
-A successfully-deployed serverless application can be found in the AWS Explorer under region and CloudFormation node that the serverless application was deployed to.
-
-In the AWS Explorer, you can invoke _remote_ AWS Lambda Functions by right-clicking the Lambda node and selecting "Invoke on AWS".
-
-Similarly, if the Function declaration contained an API Gateway event, the API Gateway API can be found in the API Gateway node under the region node the serverless application was deployed to, and can be invoked via right-clicking the API node and selecting "Invoke on AWS".
-
-## Resources
-
-General information about this SAM project can be found in the [`README.md`](./README.md) file in this folder.
-
-More information about using the AWS Toolkit For Visual Studio Code with serverless applications can be found [in the AWS documentation](https://docs.aws.amazon.com/toolkit-for-vscode/latest/userguide/serverless-apps.html) .

package/lambda-nodejs22.x/README.md

@@ -1,127 +0,0 @@
-# lambda-nodejs22.x
-
-This project contains source code and supporting files for a serverless application that you can deploy with the SAM CLI. It includes the following files and folders.
-
-- hello-world - Code for the application's Lambda function.
-- events - Invocation events that you can use to invoke the function.
-- hello-world/tests - Unit tests for the application code. 
-- template.yaml - A template that defines the application's AWS resources.
-
-The application uses several AWS resources, including Lambda functions and an API Gateway API. These resources are defined in the `template.yaml` file in this project. You can update the template to add AWS resources through the same deployment process that updates your application code.
-
-If you prefer to use an integrated development environment (IDE) to build and test your application, you can use the AWS Toolkit.  
-The AWS Toolkit is an open source plug-in for popular IDEs that uses the SAM CLI to build and deploy serverless applications on AWS. The AWS Toolkit also adds a simplified step-through debugging experience for Lambda function code. See the following links to get started.
-
-* [CLion](https://docs.aws.amazon.com/toolkit-for-jetbrains/latest/userguide/welcome.html)
-* [GoLand](https://docs.aws.amazon.com/toolkit-for-jetbrains/latest/userguide/welcome.html)
-* [IntelliJ](https://docs.aws.amazon.com/toolkit-for-jetbrains/latest/userguide/welcome.html)
-* [WebStorm](https://docs.aws.amazon.com/toolkit-for-jetbrains/latest/userguide/welcome.html)
-* [Rider](https://docs.aws.amazon.com/toolkit-for-jetbrains/latest/userguide/welcome.html)
-* [PhpStorm](https://docs.aws.amazon.com/toolkit-for-jetbrains/latest/userguide/welcome.html)
-* [PyCharm](https://docs.aws.amazon.com/toolkit-for-jetbrains/latest/userguide/welcome.html)
-* [RubyMine](https://docs.aws.amazon.com/toolkit-for-jetbrains/latest/userguide/welcome.html)
-* [DataGrip](https://docs.aws.amazon.com/toolkit-for-jetbrains/latest/userguide/welcome.html)
-* [VS Code](https://docs.aws.amazon.com/toolkit-for-vscode/latest/userguide/welcome.html)
-* [Visual Studio](https://docs.aws.amazon.com/toolkit-for-visual-studio/latest/user-guide/welcome.html)
-
-## Deploy the sample application
-
-The Serverless Application Model Command Line Interface (SAM CLI) is an extension of the AWS CLI that adds functionality for building and testing Lambda applications. It uses Docker to run your functions in an Amazon Linux environment that matches Lambda. It can also emulate your application's build environment and API.
-
-To use the SAM CLI, you need the following tools.
-
-* SAM CLI - [Install the SAM CLI](https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/serverless-sam-cli-install.html)
-* Node.js - [Install Node.js 22](https://nodejs.org/en/), including the NPM package management tool.
-* Docker - [Install Docker community edition](https://hub.docker.com/search/?type=edition&offering=community)
-
-To build and deploy your application for the first time, run the following in your shell:
-
-```bash
-sam build
-sam deploy --guided
-```
-
-The first command will build the source of your application. The second command will package and deploy your application to AWS, with a series of prompts:
-
-* **Stack Name**: The name of the stack to deploy to CloudFormation. This should be unique to your account and region, and a good starting point would be something matching your project name.
-* **AWS Region**: The AWS region you want to deploy your app to.
-* **Confirm changes before deploy**: If set to yes, any change sets will be shown to you before execution for manual review. If set to no, the AWS SAM CLI will automatically deploy application changes.
-* **Allow SAM CLI IAM role creation**: Many AWS SAM templates, including this example, create AWS IAM roles required for the AWS Lambda function(s) included to access AWS services. By default, these are scoped down to minimum required permissions. To deploy an AWS CloudFormation stack which creates or modifies IAM roles, the `CAPABILITY_IAM` value for `capabilities` must be provided. If permission isn't provided through this prompt, to deploy this example you must explicitly pass `--capabilities CAPABILITY_IAM` to the `sam deploy` command.
-* **Save arguments to samconfig.toml**: If set to yes, your choices will be saved to a configuration file inside the project, so that in the future you can just re-run `sam deploy` without parameters to deploy changes to your application.
-
-You can find your API Gateway Endpoint URL in the output values displayed after deployment.
-
-## Use the SAM CLI to build and test locally
-
-Build your application with the `sam build` command.
-
-```bash
-lambda-nodejs22.x$ sam build
-```
-
-The SAM CLI installs dependencies defined in `hello-world/package.json`, creates a deployment package, and saves it in the `.aws-sam/build` folder.
-
-Test a single function by invoking it directly with a test event. An event is a JSON document that represents the input that the function receives from the event source. Test events are included in the `events` folder in this project.
-
-Run functions locally and invoke them with the `sam local invoke` command.
-
-```bash
-lambda-nodejs22.x$ sam local invoke HelloWorldFunction --event events/event.json
-```
-
-The SAM CLI can also emulate your application's API. Use the `sam local start-api` to run the API locally on port 3000.
-
-```bash
-lambda-nodejs22.x$ sam local start-api
-lambda-nodejs22.x$ curl http://localhost:3000/
-```
-
-The SAM CLI reads the application template to determine the API's routes and the functions that they invoke. The `Events` property on each function's definition includes the route and method for each path.
-
-```yaml
-      Events:
-        HelloWorld:
-          Type: Api
-          Properties:
-            Path: /hello
-            Method: get
-```
-
-## Add a resource to your application
-The application template uses AWS Serverless Application Model (AWS SAM) to define application resources. AWS SAM is an extension of AWS CloudFormation with a simpler syntax for configuring common serverless application resources such as functions, triggers, and APIs. For resources not included in [the SAM specification](https://github.com/awslabs/serverless-application-model/blob/master/versions/2016-10-31.md), you can use standard [AWS CloudFormation](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-template-resource-type-ref.html) resource types.
-
-## Fetch, tail, and filter Lambda function logs
-
-To simplify troubleshooting, SAM CLI has a command called `sam logs`. `sam logs` lets you fetch logs generated by your deployed Lambda function from the command line. In addition to printing the logs on the terminal, this command has several nifty features to help you quickly find the bug.
-
-`NOTE`: This command works for all AWS Lambda functions; not just the ones you deploy using SAM.
-
-```bash
-lambda-nodejs22.x$ sam logs -n HelloWorldFunction --stack-name lambda-nodejs22.x --tail
-```
-
-You can find more information and examples about filtering Lambda function logs in the [SAM CLI Documentation](https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/serverless-sam-cli-logging.html).
-
-## Unit tests
-
-Tests are defined in the `hello-world/tests` folder in this project. Use NPM to install the [Mocha test framework](https://mochajs.org/) and run unit tests.
-
-```bash
-lambda-nodejs22.x$ cd hello-world
-hello-world$ npm install
-hello-world$ npm run test
-```
-
-## Cleanup
-
-To delete the sample application that you created, use the AWS CLI. Assuming you used your project name for the stack name, you can run the following:
-
-```bash
-sam delete --stack-name lambda-nodejs22.x
-```
-
-## Resources
-
-See the [AWS SAM developer guide](https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/what-is-sam.html) for an introduction to SAM specification, the SAM CLI, and serverless application concepts.
-
-Next, you can use AWS Serverless Application Repository to deploy ready to use Apps that go beyond hello world samples and learn how authors developed their applications: [AWS Serverless Application Repository main page](https://aws.amazon.com/serverless/serverlessrepo/)

package/lambda-nodejs22.x/events/event.json

@@ -1,62 +0,0 @@
-{
-  "body": "{\"message\": \"hello world\"}",
-  "resource": "/{proxy+}",
-  "path": "/path/to/resource",
-  "httpMethod": "POST",
-  "isBase64Encoded": false,
-  "queryStringParameters": {
-    "foo": "bar"
-  },
-  "pathParameters": {
-    "proxy": "/path/to/resource"
-  },
-  "stageVariables": {
-    "baz": "qux"
-  },
-  "headers": {
-    "Accept": "text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8",
-    "Accept-Encoding": "gzip, deflate, sdch",
-    "Accept-Language": "en-US,en;q=0.8",
-    "Cache-Control": "max-age=0",
-    "CloudFront-Forwarded-Proto": "https",
-    "CloudFront-Is-Desktop-Viewer": "true",
-    "CloudFront-Is-Mobile-Viewer": "false",
-    "CloudFront-Is-SmartTV-Viewer": "false",
-    "CloudFront-Is-Tablet-Viewer": "false",
-    "CloudFront-Viewer-Country": "US",
-    "Host": "1234567890.execute-api.us-east-1.amazonaws.com",
-    "Upgrade-Insecure-Requests": "1",
-    "User-Agent": "Custom User Agent String",
-    "Via": "1.1 08f323deadbeefa7af34d5feb414ce27.cloudfront.net (CloudFront)",
-    "X-Amz-Cf-Id": "cDehVQoZnx43VYQb9j2-nvCh-9z396Uhbp027Y2JvkCPNLmGJHqlaA==",
-    "X-Forwarded-For": "127.0.0.1, 127.0.0.2",
-    "X-Forwarded-Port": "443",
-    "X-Forwarded-Proto": "https"
-  },
-  "requestContext": {
-    "accountId": "123456789012",
-    "resourceId": "123456",
-    "stage": "prod",
-    "requestId": "c6af9ac6-7b61-11e6-9a41-93e8deadbeef",
-    "requestTime": "09/Apr/2015:12:34:56 +0000",
-    "requestTimeEpoch": 1428582896000,
-    "identity": {
-      "cognitoIdentityPoolId": null,
-      "accountId": null,
-      "cognitoIdentityId": null,
-      "caller": null,
-      "accessKey": null,
-      "sourceIp": "127.0.0.1",
-      "cognitoAuthenticationType": null,
-      "cognitoAuthenticationProvider": null,
-      "userArn": null,
-      "userAgent": "Custom User Agent String",
-      "user": null
-    },
-    "path": "/prod/path/to/resource",
-    "resourcePath": "/{proxy+}",
-    "httpMethod": "POST",
-    "apiId": "1234567890",
-    "protocol": "HTTP/1.1"
-  }
-}

package/lambda-nodejs22.x/hello-world/app.mjs

@@ -1,82 +0,0 @@
-/**
- *
- * Event doc: https://docs.aws.amazon.com/apigateway/latest/developerguide/set-up-lambda-proxy-integrations.html#api-gateway-simple-proxy-for-lambda-input-format
- * @param {Object} event - API Gateway Lambda Proxy Input Format
- *
- * Context doc: https://docs.aws.amazon.com/lambda/latest/dg/nodejs-prog-model-context.html
- * @param {Object} context
- *
- * Return doc: https://docs.aws.amazon.com/apigateway/latest/developerguide/set-up-lambda-proxy-integrations.html
- * @returns {Object} object - API Gateway Lambda Proxy Output Format
- *
- */
-
-import { Logger } from '@aws-lambda-powertools/logger';
-const logger = new Logger({ serviceName: 'serverlessAirline' });
-import Ajv from 'ajv';
-import {cache, catalog} from "cats-a-logs/index.js";
-
-export const lambdaHandler = async (event, context) => {
-  const response = {
-    statusCode: 200,
-    body: JSON.stringify({
-      message: 'hello world',
-    }),
-  };
-  let kilos = Math.ceil(Math.random()*70);
-  let pounds =Math.ceil(Math.random()*35);
-  let grams = Math.ceil(Math.random()*20);
-  catalog(pounds, 'poundsTest', 'lambda-junction-metrics2', 'None', {
-    functionVersion: '$LATEST',
-    testDimension: 'berp',
-  });
-  catalog(grams, 'randomTest', 'lambda-junction-metrics2', 'Count', {
-    testDimension: 'berp',
-    functionVersion: '$LATEST',
-  });
-  // catalog(kilos, 'level', 'lambda-junction-metrics2');
-  catalog(
-    kilos,
-    'Weight',
-    'lambda-junction-metrics2',
-    'None',
-    { functionVersion: '$LATEST', testDimension: 'berp' },
-    60,
-    true
-  );
-  
-  //catalog(pounds, "testLogger2" , "lambda-function-metrics", Milliseconds, {'functionVersion': $LATEST, 'testDimension': derp});
-
-  //catalog(trackedVariable: var, metricName: string , metricNamespace: string, metricUnitLabel: string, CustomerDefinedDimension(s): Object {DimensionName: DimensionValue: String, ...}, ...);
-
-  // logger.info('testEMF using logger.info', {
-  //   testguy: "hi",
-  //   kilos: 54,
-  //   testLogger2: 34,
-  //   functionVersion: "$LATEST",
-  //   testDimension: "derp",
-  //   _aws: {
-  //     Timestamp: Date.now(),
-  //     CloudWatchMetrics: [
-  //       {
-  //         Namespace: "lambda-function-metrics",
-  //         Dimensions: [["functionVersion", "testDimension"]],
-  //         Metrics: [
-  //           {
-  //             Name: "kilos",
-  //             Unit: "Kilograms",
-  //             StorageResolution: 60
-  //           },
-  //           {
-  //             Name: "testLogger2",
-  //             Unit: "Milliseconds",
-  //             StorageResolution: 60
-  //           }
-  //         ]
-  //       }
-  //     ]
-  //   },
-  // });
-
-  return response;
-};

package/lambda-nodejs22.x/hello-world/package.json

@@ -1,25 +0,0 @@
-{
-  "name": "hello_world",
-  "version": "1.0.0",
-  "description": "hello world sample for NodeJS",
-  "main": "app.js",
-  "repository": "https://github.com/awslabs/aws-sam-cli/tree/develop/samcli/local/init/templates/cookiecutter-aws-sam-hello-nodejs",
-  "author": "SAM CLI",
-  "license": "MIT",
-  "dependencies": {
-    "axios": ">=1.6.0",
-    "@aws-lambda-powertools/logger": "^2.11.0",
-    "@aws-lambda-powertools/metrics": "^2.11.0",
-    "lambda-log": "^3.1.0",
-    "ajv": "^8.17.1",
-    "cats-a-logs": "^1.0.1"
-  },
-  "scripts": {
-    "test": "mocha tests/unit/"
-  },
-  "devDependencies": {
-    "chai": "^4.3.6",
-    "mocha": "^10.2.0"
-    
-  }
-}

package/lambda-nodejs22.x/samconfig.toml

@@ -1,31 +0,0 @@
-version = 0.1
-
-[default.global.parameters]
-stack_name = "catalog-dev-v1"
-region = "us-east-2"
-
-[default.build.parameters]
-cached = true
-parallel = true
-
-[default.validate.parameters]
-lint = true
-
-[default.deploy.parameters]
-capabilities = "CAPABILITY_IAM"
-confirm_changeset = true
-resolve_s3 = true
-
-[default.package.parameters]
-resolve_s3 = true
-
-[default.sync.parameters]
-watch = true
-template_file = "/Users/clara/code/codesmith/cat-a-log/lambda-nodejs22.x/template.yaml"
-dependency_layer = false
-
-[default.local_start_api.parameters]
-warm_containers = "EAGER"
-
-[default.local_start_lambda.parameters]
-warm_containers = "EAGER"

package/lambda-nodejs22.x/template.yaml

@@ -1,41 +0,0 @@
-AWSTemplateFormatVersion: '2010-09-09'
-Transform: AWS::Serverless-2016-10-31
-Description: >
-  lambda-nodejs22.x
-
-  Sample SAM Template for lambda-nodejs22.x
-  
-# More info about Globals: https://github.com/awslabs/serverless-application-model/blob/master/docs/globals.rst
-Globals:
-  Function:
-    Timeout: 3
-
-Resources:
-  HelloWorldFunction:
-    Type: AWS::Serverless::Function # More info about Function Resource: https://github.com/awslabs/serverless-application-model/blob/master/versions/2016-10-31.md#awsserverlessfunction
-    Properties:
-      CodeUri: hello-world/
-      Handler: app.lambdaHandler
-      Runtime: nodejs22.x
-      Architectures:
-        - x86_64
-      Events:
-        HelloWorld:
-          Type: Api # More info about API Event Source: https://github.com/awslabs/serverless-application-model/blob/master/versions/2016-10-31.md#api
-          Properties:
-            Path: /hello
-            Method: get
-
-Outputs:
-  # ServerlessRestApi is an implicit API created out of Events key under Serverless::Function
-  # Find out more about other implicit resources you can reference within SAM
-  # https://github.com/awslabs/serverless-application-model/blob/master/docs/internals/generated_resources.rst#api
-  HelloWorldApi:
-    Description: "API Gateway endpoint URL for Prod stage for Hello World function"
-    Value: !Sub "https://${ServerlessRestApi}.execute-api.${AWS::Region}.amazonaws.com/Prod/hello/"
-  HelloWorldFunction:
-    Description: "Hello World Lambda Function ARN"
-    Value: !GetAtt HelloWorldFunction.Arn
-  HelloWorldFunctionIamRole:
-    Description: "Implicit IAM Role created for Hello World function"
-    Value: !GetAtt HelloWorldFunctionRole.Arn

package/postcss.config.js

@@ -1,7 +0,0 @@
-const tailwindcss = require('tailwindcss');
-module.exports = {
-  plugins: [
-    'postcss-preset-env',
-    tailwindcss
-  ],
-};

package/server/server.ts

@@ -1,4 +0,0 @@
-const express = require('express');
-const path = require('path');
-
-const app = express();

package/tailwind.config.js

@@ -1,12 +0,0 @@
-/** @type {import('tailwindcss').Config} */
-module.exports = {
-  content: ['./client/*.html'],/////TODO: POTENTIAL PROBLEM
-  theme: {
-    extend: {},
-  },
-  variants: {
-    extend: {},
-  },
-  plugins: [],
-}
-

package/webpack.config.js

@@ -1,79 +0,0 @@
-const path = require('path');
-const HtmlWebpackPlugin = require('html-webpack-plugin');
-// const BundleAnalyzerPlugin = require('webpack-bundle-analyzer').BundleAnalyzerPlugin
-
-module.exports = {
-  mode: 'development',
-  entry: {
-    bundle: path.resolve(__dirname, 'client/index.ts'), // Entry point name is 'bundle'
-  },
-  output: {
-    path: path.resolve(__dirname, 'dist'),
-    filename: '[name][contenthash].js', // Filename template for JS bundles.  Assigns bundle to [name], [contenthash] appends a unique hash to each rebuild of bundle.
-    clean: true, // Cleans old files in the output directory before each build
-    assetModuleFilename: '[name][ext]', // Template for assets file names & their file extensions
-  },
-  //maps from bundle to source creating bundle.map file.  Apparently helpful for debugging w/in the bundle...?
-  devtool: 'source-map',
-  devServer: {
-    static: {
-      directory: path.resolve(__dirname, 'dist'), // serve static files from 'dist'
-    },
-    //changed from 3000 to 8080
-    port: 8080,
-    open: true, // Automatically opens browser when server starts
-    hot: true, //  Enables Hot Module Replacement (HMR) w/out reloading/refreshing the whole page
-    compress: true,
-    historyApiFallback: true, //unknown routes redirect user to index.html..?
-  },
-  // Enable importing JS / JSX files without specifying their extension
-  resolve: {
-    extensions: ['.js', '.jsx', '.json', '.ts', '.tsx'], 
-  },
-  module: {
-    rules: [
-      {
-        test: /\.ts?$/,
-        use: 'ts-loader',
-        exclude: /node_modules/,////// TODO: POTENTIAL PROBLEM
-      },
-      {
-        test: /\.scss$/,
-        use: ['style-loader', 'css-loader', 'sass-loader'],
-      },
-      { test: /\.css$/, 
-        use: ['style-loader', 'css-loader', 'postcss-loader'] },
-      {
-        test: /\.(png|svg|jpg|jpeg|gif)$/i,
-        type: 'asset/resource',
-      },
-      {
-        test: /\.(js|jsx)$/,
-        exclude: /node_modules/,
-        use: {
-          loader: 'babel-loader',
-          // options: {
-          //   //presets are defined in my .babelrc file including preset for react
-          //     presets: ['@babel/preset-env']
-          // },
-        },
-      },
-      {
-        //for being able to load images
-        test: /\.(png|svg|jpg|jpeg|gif)$/i,
-        type: 'asset/resource',
-      },
-    ],
-  },
-  // resolve: {
-  //   extensions: ['.js', '.jsx'],
-  // },
-  plugins: [
-    new HtmlWebpackPlugin({
-      title: 'Cat-A-Log',
-      filename: 'index.html',
-      template: 'client/template.html', //relative path of template.html
-    }),
-    // new BundleAnalyzerPlugin(),
-  ],
-};