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

slseasyrouting

v1.2.6

Published

A lib to easily make routes in lambdas using the Serverless Framework

Downloads

366

Readme

SLS Easy Routing

A lib to easily make routes in lambdas using the Serverless Framework

🤔 Why would I use it?

Sometimes there is no need of having multiple lambdas, for example, let's suppose we have one lambda to get the user email and other lambda to get the user phone number. In this case, we could have only one lambda with two endpoints, /email and /phone. Doing this way, you will have a much more organized AWS and it will be possible to separate lambdas by domain. To make this, you would need to create something to handle the requests incoming, by checking the path and method and then, if matching, run a certain function. With this lib, you can easily do this :)

💻 Requirements

You can find how to this here

💽 Installation

hello@world:~$ yarn add slseasyrouting

or

hello@world:~$ npm i slseasyrouting

🚀 Usage

First, you'll need to enable decorators in your typescript project. You can achieve that by adding this line under compilerOptions in your tsconfig.json:

"experimentalDecorators": true

Now you have to configure your serverless to accept any request to any endpoint. Here is my serverless.yml function config:

 functions: {
    main: {
      handler: hello.handler,
      events: [
        {
          http: {
            method: 'ANY',
            path: '/',
          },
        },
        {
          http: {
            method: 'ANY',
            path: '{proxy+}',
          },
        },
      ],
    },
  },

After this, you'll need to create a routes file, I recommend something like routes.ts, inside it, create a class called Routes and add the @Route decorator, inside the class, add a constructor containing the event and then the methods with the desired decorator, check the example:

import { getDate, hello } from "./services/hello.service";
import { Route, Post, Get } from "slseasyrouting";

@Route
export class Routes {
  constructor(private readonly event: any) {}

  @Post("/")
  async helloRoute(event) {
    return await hello(event.body.name);
  }

  @Get("/")
  async getTodaysDate() {
    return await getDate();
  }
}

Then, at your handler.ts file, add return new Routes(event), it will look like this:

import { middyfy } from '@libs/lambda';
import { Routes } from './routes';

const handler = async (event) => {
  console.log(event);
  return new Routes(event);
};

export const main = middyfy(handler);

Inside the decorator, you can pass the desired endpoint, for example, @Get('/users/email').

This lib contains some responses too in case you want to use, for example, if you want to throw a 401, you can use return UnAuthorized(). You can pass a custom message too by providing it inside the function parameters, for example: return UnAuthorized('Get out!').

🗿 Responses

As said before, this lib contains some functions that you can call for responses. At the moment we have:

| function | status code | |--------------------|-------------| | UnAuthorized | 401 | | NotFound | 404 | | Gone | 410 | | BadRequest | 400 | | ServiceUnavailable | 503 | | Success | 200 |