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

generic-rest-api-router

v1.2.0

Published

A simple, generic REST API router for use with serverless functions.

Downloads

7

Readme

generic-rest-api-router

A simple, generic REST API router for use with serverless functions.

Installation

  • npm i generic-rest-api-router

Basic usage

This project is only intended to be a base to be extended for a specific environment. In order to apply the generic-rest-api-router to an environment, you need to implement the RequestContext interface.

For example, for usage within AWS Lambda, you could define the following AWSRequestContext:

export class AwsRequestContext implements RequestContext {
  constructor(public event: APIGatewayProxyEvent, public context: Context) {
  }

  getHttpMethod(): string {
    return this.event.httpMethod;
  }

  getPath(): string {
    return this.event.path;
  }
  
  getBody(): string {
    return this.event.body || '';
  }
}

You can then extend the FunctionRouter to define the templated classes that will be used in the Handler functions:

export class AwsFunctionRouter<T> extends FunctionRouter<T, AwsRequestContext> {
  async handle(requestContext: AwsRequestContext): Promise<APIGatewayProxyResult> {
    const response = await super.handleRequest(requestContext);

    return {
      headers: response.headers,
      statusCode: response.statusCode,
      body: response.body || ''
    }
  }
}

Once these classes been defined, you can then create your routes in a Lambda function:

const router = new AwsFunctionRouter({
    resourcePath: '/post-service',
    includeCORS: true
  })
  .get('', async (route) => {
    const postRepository = new PostRepository();

    return route.okResponse(await postRepository.findAll());
  })
  .get('/:id', async (route, requestContext) => {
    const postRepository = new PostRepository();

    const id = route.getPathParams(requestContext).id;
    const post = await postRepository.findPostById(id);

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

    return route.okResponse(post);
  });

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

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