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

aws-rest-api-router

v1.0.0

Published

A simple Typescript-based REST API router for use with AWS Lambda functions.

Downloads

41

Readme

aws-rest-api-router

A simple Typescript-based REST API router for use with AWS Lambda functions.

Introduction

A simple way to route your REST API requests and eliminate boilerplate without the need for extensive libraries or configuration. The implementation has a very small footprint.

Provides the following:

  • HTTP Method / Path routing
  • Access to path parameters
  • Body parsing to JSON
  • Error handling
  • Eliminates boilerplate

Installation

  • npm i aws-rest-api-router

Basic usage

This module provides a simple routing mechanism for defining REST APIs within AWS Lambda functions. Codes speaks better than words, so the following Lambda function definition demonstrates how the AwsFunctionRouter can be used to define a group of REST API routes:

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

import { AwsFunctionRouter, AwsRequestContext } from 'aws-rest-api-router';

import { PostRepository } from './PostRepository';

const postRepository = new PostRepository();

// define the router with a basePath which should match the URI for your Lambda's API Gateway
const router = new AwsFunctionRouter<Post>({
    basePath: '/post-service',
    includeCORS: true
  })
  .get('', async (route) => {
    // GET http://my-aws-url/post-service
    return route.okResponse(await postRepository.findAll());
  })
  .get('/:id', async (route, requestContext) => {
    // GET http://my-aws-url/post-service/1
    const id = route.getPathParams(requestContext).id;
    const post = await postRepository.findPostById(id);

    if (!post) {
      return route.errorResponse(StatusCodes.NOT_FOUND);
    }

    return route.okResponse(post);
  })
  .post('', async (route, requestContext) => {
    // POST http://my-aws-url/post-service
    // { "title": "My first post", "content": "This is my first post" }
    const post = await postRepository.save(route.parseBody(requestContext));

    return route.okResponse(post);
  })
  .update('/:id', async (route, requestContext) => {
    // PUT http://my-aws-url/post-service/1
    // { "id": "1", "title": "My first post", "content": "This is my first post" }
    const id = route.getPathParams(requestContext).id;
    const post = await postRepository.findPostById(id);

    if (!post) {
      return route.errorResponse(StatusCodes.NOT_FOUND);
    }

    const postUpdates = route.parseBody(requestContext);

    post.title = postUpdates.title;
    post.content = postUpdates.content;

    postRepository.update(post);

    return route.okResponse(post);
  });

export const lambdaHandler = async (event: APIGatewayProxyEvent, context: Context): Promise<APIGatewayProxyResult> => {
  return await router.handle(new AwsRequestContext(event, context));
};

Note that getting path params relies on using an AWS proxy resource within your API Gateway definition.

You can find a working example in aws-sam-rest-api-starter.