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

express-requesthandler

v0.0.17

Published

Allows creating express routes automatically from class methods using decorators

Downloads

22

Readme

The example below shows how to use this package in a class. It is advised to create a separate file for each set of routes and export the routes as shown below. Supported types for parameters are string, number, boolean, ObjectID and Date which means these types will automatically be type-checked. For more complex types, the type of the parameter cannot be assumed and should be checked manually.

import express from "express";

import { ExpressError, get, post, use } from "express-requesthandler";

export class Routes {
    // The router which will be populated by the generated routes
    public static router: express.Router = express.Router();

    // This is a GET route which gets its parameters from the query parameters
    @get()
    public static someRoute1(param1: string, param2: number): void {
        // Throw an ExpressError to set the status code of the response
        throw new ExpressError("Not found", 404);
    }

    // This is a POST route which gets its parameters from either the query parameters or the body
    @post()
    public static someRoute2(param1: string, param2: number): void {

    }

    // This is a middleware route
    // The return value of this route will be available in the next route under the identifier "user"
    @use(true)
    public static someRoute3(param1: string, param2: number): { user: string } {
        return { user: "userId" };
    }

    // This is an example of how to use the previous middleware function
    @get()
    public static someRoute4(user: string): void {
        // The parameter user should now be "userId"
    }
}

export default Routes.router;

The router can then be used as follows.

import express from "express";
import routes from "./routes";

const app = express();

app.use("/routes", routes);

// Listen
app.listen(3000, () => {
    console.log("Listening on port 3000");
});