npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

lambda-mechanic

v0.5.0

Published

Tiny NodeJS server that mocks AWS Lambda requests for local development

Downloads

4

Readme

Lambda Mechanic

Lambda Mechanic

Tiny NodeJS server that mocks AWS Lambda requests for local development.

Usage

Install the library and dependencies

% npm install -d lambda-mechanic node-dev

If you're using Typescript you can opt for ts-node-dev

% npm install -d lambda-mechanic ts-node-dev

Create a simple script called server.js with the following content:

const { Mechanic } = require('lambda-mechanic');

// adjust to import your Lambda handler function
import { handler } from './src';

const mechanic = new Mechanic(
  [
    ['/', handler],
    ['/test', async () => ({ statusCode: 200, body: 'Test' })],
  ],
  { port: 3001 },
);

mechanic.listen();

Or for Typescript, create a script called server.ts with the following content:

import { Mechanic } from 'lambda-mechanic';

// adjust to import your Lambda handler function
import { handler } from './src';

const mechanic = new Mechanic(
  [
    ['/', handler],
    ['/test', async () => ({ statusCode: 200, body: 'Test' })],
  ],
  { port: 3001 },
);

mechanic.listen();

In a new terminal window run:

% npx node-dev server.js

Or for Typescript:

% npx ts-node-dev server.ts

You can now experiment with your Lambda handler by sending requests to https://localhost:3000.

API

Mechanic constructor

The Mechanic constructor expects two paramters on instantiation, an array of handler "tuples" and an options object:

new Mechanic(
  handler: HandlerTuple[],
  options: MechanicOptions,
)

HandlerTuple array

The handler "tuple" describes a route and handler function pairing.

Technically it is a Javascript array with a route string (or regular expression) at the first index and a handler function at the second index.

String example:

const handler = async () => ({ statusCode: 200, body: 'Hello World!' });

const route = ['/path', handler];

RegEx example:

const handler = async () => ({ statusCode: 200, body: 'Handles everything...' });

const route = [/.*/, handler];

Handler function

The handler function expects an event that conforms to the Lambda APIGatewayProxyEvent interface and returns a promise that resolves an object that confirms to the APIGatewayProxyResult interface.

If you're using Typescript the types can be imported from the aws-lambda package.

import { APIGatewayProxyEvent, APIGatewayProxyResult } from 'aws-lambda';

const handler = async (
  event: APIGatewayProxyEvent,
): Promise<APIGatewayProxyResult> => ({
  statusCode: 200,
  body: 'Hello World!',
});

MechanicOptions object

There are currently only two options port and headers. The defaults are:

const defaultOptions = {
  port: 3000,
  headers: {},
};

The options interface is:

interface MechanicOptions {
  port?: number;
  headers?: {
    [key: string]: string;
  };
}

Bugs & Issues

If you spot bugs please open an issue.