prettier

Author: janaz

.github/workflows/main.yml

@@ -9,13 +9,13 @@ jobs:
     runs-on: ubuntu-latest
     strategy:
       matrix:
-        node: [ '14', '16', '18' ]
+        node: ["14", "16", "18"]
     name: Node ${{ matrix.node }}
 
     steps:
-    - uses: actions/checkout@v3
-    - uses: actions/setup-node@v3
-      with:
-        node-version: ${{ matrix.node }}
-    - run: npm install
-    - run: npm test
+      - uses: actions/checkout@v3
+      - uses: actions/setup-node@v3
+        with:
+          node-version: ${{ matrix.node }}
+      - run: npm install
+      - run: npm test

.gitignore

@@ -2,3 +2,6 @@ node_modules
 *tgz
 /dist
 coverage
+public
+views
+

.prettierignore

@@ -0,0 +1,11 @@
+static
+node_modules
+coverage
+__sapper__
+src/parser
+.vscode
+package-lock.json
+.svelte-kit
+build
+dist
+

.prettierrc

@@ -0,0 +1,4 @@
+{
+  "semi": false,
+  "bracketSameLine": true
+}

.vscode/css-custom-data.json

@@ -0,0 +1,55 @@
+{
+  "version": 1.1,
+  "atDirectives": [
+    {
+      "name": "@tailwind",
+      "description": "Use the `@tailwind` directive to insert Tailwind's `base`, `components`, `utilities` and `screens` styles into your CSS.",
+      "references": [
+        {
+          "name": "Tailwind Documentation",
+          "url": "https://tailwindcss.com/docs/functions-and-directives#tailwind"
+        }
+      ]
+    },
+    {
+      "name": "@responsive",
+      "description": "You can generate responsive variants of your own classes by wrapping their definitions in the `@responsive` directive:\n```css\n@responsive {\n  .alert {\n    background-color: #E53E3E;\n  }\n}\n```\n",
+      "references": [
+        {
+          "name": "Tailwind Documentation",
+          "url": "https://tailwindcss.com/docs/functions-and-directives#responsive"
+        }
+      ]
+    },
+    {
+      "name": "@screen",
+      "description": "The `@screen` directive allows you to create media queries that reference your breakpoints by **name** instead of duplicating their values in your own CSS:\n```css\n@screen sm {\n  /* ... */\n}\n```\n…gets transformed into this:\n```css\n@media (min-width: 640px) {\n  /* ... */\n}\n```\n",
+      "references": [
+        {
+          "name": "Tailwind Documentation",
+          "url": "https://tailwindcss.com/docs/functions-and-directives#screen"
+        }
+      ]
+    },
+    {
+      "name": "@variants",
+      "description": "Generate `hover`, `focus`, `active` and other **variants** of your own utilities by wrapping their definitions in the `@variants` directive:\n```css\n@variants hover, focus {\n   .btn-brand {\n    background-color: #3182CE;\n  }\n}\n```\n",
+      "references": [
+        {
+          "name": "Tailwind Documentation",
+          "url": "https://tailwindcss.com/docs/functions-and-directives#variants"
+        }
+      ]
+    },
+    {
+      "name": "@apply",
+      "description": "Use @apply to inline any existing utility classes into your own custom CSS.",
+      "references": [
+        {
+          "name": "Tailwind Documentation",
+          "url": "https://tailwindcss.com/docs/functions-and-directives#apply"
+        }
+      ]
+    }
+  ]
+}

.vscode/extensions.json

@@ -0,0 +1 @@
+{ "recommendations": ["svelte.svelte-vscode"] }

.vscode/launch.json

@@ -0,0 +1,15 @@
+{
+  // Use IntelliSense to learn about possible attributes.
+  // Hover to view descriptions of existing attributes.
+  // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
+  "version": "0.2.0",
+  "configurations": [
+    {
+      "type": "pwa-chrome",
+      "request": "launch",
+      "name": "Launch Chrome against localhost",
+      "url": "http://localhost:3000",
+      "webRoot": "${workspaceFolder}"
+    }
+  ]
+}

.vscode/settings.json

@@ -0,0 +1,5 @@
+{
+  "prettier.configPath": ".prettierrc",
+  "editor.formatOnSave": true,
+  "css.customData": [".vscode/css-custom-data.json"]
+}

README.md

@@ -5,30 +5,33 @@ An npm module that allows your Node.js web applications to be deployed as an AWS
 [![Build Status](https://travis-ci.org/janaz/lambda-request-handler.svg?branch=master)](https://travis-ci.org/janaz/lambda-request-handler)
 
 The list of supported frameworks matches [in-process-request](https://github.com/janaz/in-process-request)
-* Express.js v3
-* Express.js v4
-* Express.js v5
-* Apollo Server v2
-* Hapi v19 (only supported in `nodejs12.x` runtime)
-* Hapi v20 (only supported in `nodejs12.x` runtime)
-* NestJS v7
-* Connect v3
-* Koa v2
-* Polka
-* Fastify v3
+
+- Express.js v3
+- Express.js v4
+- Express.js v5
+- Apollo Server v2
+- Hapi v19 (only supported in `nodejs12.x` runtime)
+- Hapi v20 (only supported in `nodejs12.x` runtime)
+- NestJS v7
+- Connect v3
+- Koa v2
+- Polka
+- Fastify v3
 
 Inspired by [aws-serverless-express](https://github.com/awslabs/aws-serverless-express)
 
 It supports `nodejs10.x` and `nodejs12.x` execution environments.
 
 The main differences between this module and `aws-serverless-express` are
-* It's using [in-process-request](https://github.com/janaz/in-process-request) module to execute app handlers in-process without having to start background http server
-* Simpler setup as it doesn't require managing the internal http server
-* Support for applications that require asynchronous setup (for example reading config from network, or decrypting secrets from KMS)
-* It's faster, because it doesn't need to pass the request to the internal server through the unix socket
-* It's free from issues caused by limits in Node.js http module such as header size limit
+
+- It's using [in-process-request](https://github.com/janaz/in-process-request) module to execute app handlers in-process without having to start background http server
+- Simpler setup as it doesn't require managing the internal http server
+- Support for applications that require asynchronous setup (for example reading config from network, or decrypting secrets from KMS)
+- It's faster, because it doesn't need to pass the request to the internal server through the unix socket
+- It's free from issues caused by limits in Node.js http module such as header size limit
 
 The handler supports events from the following sources:
+
 - API Gateway [REST APIs](https://docs.aws.amazon.com/apigateway/latest/developerguide/apigateway-rest-api.html)
 - API Gateway [HTTP APIs](https://docs.aws.amazon.com/apigateway/latest/developerguide/http-api.html)
 - [Application Load Balancer](https://docs.aws.amazon.com/lambda/latest/dg/services-alb.html)
@@ -42,13 +45,15 @@ There's a [demo app](https://github.com/janaz/lambda-request-handler-example) sh
 The default export of `lambda-request-handler` is a function that takes an application handler (i.e. Express.js app instance) as an argument and returns an AWS Lambda handler function.
 
 An additional header is injected into the request
-* `x-aws-lambda-request-id` - AWS Lambda Request Id
+
+- `x-aws-lambda-request-id` - AWS Lambda Request Id
 
 ```sh
 $ npm install lambda-request-handler
 ```
 
 ### Express.js
+
 ```javascript
 const express = require('express')
 const lambdaRequestHandler = require('lambda-request-handler')
@@ -75,13 +80,13 @@ If the above file in your Lambda source was called `index.js` then the name of t
 Sometimes the application needs to read configuration from remote source before it can start processing requests. For example it may need to decrypt some secrets managed by KMS. For this use case a special helper `deferred` has been provided. It takes a factory function which returns a Promise that resolves to the app instance. The factory function will be called only once.
 
 ```javascript
-const lambdaRequestHandler = require('lambda-request-handler')
-const AWS = require('aws-sdk')
-const express = require('express')
+const lambdaRequestHandler = require("lambda-request-handler")
+const AWS = require("aws-sdk")
+const express = require("express")
 
 const createApp = (secret) => {
-  const app = express();
-  app.get('/secret', (req, res) => {
+  const app = express()
+  app.get("/secret", (req, res) => {
     res.json({
       secret: secret,
     })
@@ -90,51 +95,52 @@ const createApp = (secret) => {
 
 const myAppPromise = async () => {
   const kms = new AWS.KMS()
-  const data = await kms.decrypt({
-    CiphertextBlob: Buffer.from(process.env.ENCRYPTED_SECRET, 'base64')
-  }).promise()
-  const secret = data.Plaintext.toString('ascii')
-  return createApp(secret);
-};
+  const data = await kms
+    .decrypt({
+      CiphertextBlob: Buffer.from(process.env.ENCRYPTED_SECRET, "base64"),
+    })
+    .promise()
+  const secret = data.Plaintext.toString("ascii")
+  return createApp(secret)
+}
 
-const handler = lambdaRequestHandler.deferred(myAppPromise);
+const handler = lambdaRequestHandler.deferred(myAppPromise)
 
 module.exports = { handler }
-
 ```
 
 ### Hapi
 
 Please note that Hapi v19 dropped support for Node v10. The only AWS Lambda runtime that supports it is `nodejs12.x`.
 
 ```javascript
-const Hapi = require('@hapi/hapi')
-const lambdaRequestHandler = require('lambda-request-handler')
+const Hapi = require("@hapi/hapi")
+const lambdaRequestHandler = require("lambda-request-handler")
 
 // create custom listener for Hapi
 const myListener = new lambdaRequestHandler.HapiListener()
 
 // Pass the custom listener to Hapi.server
 const server = Hapi.server({
-  listener: myListener
-});
+  listener: myListener,
+})
 
 server.route({
-  method: 'GET',
-  path: '/',
+  method: "GET",
+  path: "/",
   handler: (_request: any, _h: any) => {
-    return 'Hello World!';
-  }
-});
+    return "Hello World!"
+  },
+})
 
 const myAppPromise = async () => {
   //wait for the server to initialize
   await server.start()
   // return the request listener function
   return myListener.handler
-};
+}
 
-const handler = lambdaRequestHandler.deferred(myAppPromise);
+const handler = lambdaRequestHandler.deferred(myAppPromise)
 
 module.exports = { handler }
 ```
@@ -146,17 +152,17 @@ If the above file in your Lambda source was called `index.js` then the name of t
 This example is in Typescript
 
 ```typescript
-import lambdaRequestHandler from 'lambda-request-handler'
+import lambdaRequestHandler from "lambda-request-handler"
 
-import { NestFactory } from '@nestjs/core';
-import { Module, Get, Controller } from '@nestjs/common';
-import { NestExpressApplication } from '@nestjs/platform-express';
+import { NestFactory } from "@nestjs/core"
+import { Module, Get, Controller } from "@nestjs/common"
+import { NestExpressApplication } from "@nestjs/platform-express"
 
 @Controller()
 class AppController {
   @Get()
   render() {
-    return { hello: 'world' };
+    return { hello: "world" }
   }
 }
 
@@ -167,12 +173,12 @@ class AppController {
 class AppModule {}
 
 const getApp = async () => {
-  const app = await NestFactory.create<NestExpressApplication>(AppModule);
+  const app = await NestFactory.create<NestExpressApplication>(AppModule)
 
-  return await lambdaRequestHandler.nestHandler(app);
+  return await lambdaRequestHandler.nestHandler(app)
 }
 
-const handler = lambdaRequestHandler.deferred(getApp);
+const handler = lambdaRequestHandler.deferred(getApp)
 
 module.exports = { handler }
 ```

jest.config.js

@@ -1,4 +1,4 @@
 module.exports = {
-  preset: 'ts-jest',
-  testMatch: [ "<rootDir>/test/**/*.(test|spec).ts" ]
-};
+  preset: "ts-jest",
+  testMatch: ["<rootDir>/test/**/*.(test|spec).ts"],
+}

package-lock.json

@@ -3,6 +3,8 @@
   "version": "0.5.1-alpha1",
   "license": "(MIT OR Apache-2.0)",
   "scripts": {
+    "prettier": "prettier --write .",
+    "prettier:ci": "prettier --check .",
     "precompile": "rm -rf dist",
     "compile": "tsc",
     "test": "jest --coverage"
@@ -53,6 +55,7 @@
     "ejs": "^3.1.6",
     "express": "^4.17.3",
     "jest": "^27.5.1",
+    "prettier": "^2.7.1",
     "ts-jest": "^27.1.4",
     "ts-node": "^10.7.0",
     "typescript": "^4.6.3"