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

tsnet-http

v1.0.7

Published

A set of TypeScript decorators for express.js inspired by the sample API project generated by .NET Core using C#.

Downloads

13

Readme

Table of Contents

  1. Why?
  2. How to use
  3. Decorators
  4. Technologies
  5. License

Why?

Working with C# and .NET 5/6 I really liked how the API Project is structured and wanted to achieve a similar experience using TypeScripts decorators to create a micro framework.

This micro frameworks allows for creating quick controllers and routes which are then automatically registered to the express server.

How to use

Caution

  1. First define a controller in a file like ./controllers/ping.controller.ts:
import { BaseController, Controller, Get } from "ts-http";
import { Request, Response } from "express";

@Controller("/")
export abstract class PingController extends BaseController {
    
    @Get("/ping")
    public static Get(req: Request, res: Response) {
        res.send("pong");
    }
}
  1. Now define a middleware in a file like ./middlewares/test.middleware.ts:
import { BaseMiddleware, Middleware, MiddlewareFunction } from "ts-http";
import { Request, Response, NextFunction } from "express";

@Middleware
export abstract class UseTest extends BaseMiddleware {

    @MiddlewareFunction("/ping") /* leave empty for global middleware */
    public static Use(req: Request, res: Response, next: NextFunction) {
        res.setHeader("ping", "pong");
        next();
    }
}
  1. Let's register our new controller and start the server in a ./index.ts:
import { Server } from "ts-http";

Server.Init({
    controllerDirs: [ "/controllers" ],
    middlewareDirs: [ "/middlewares" ],
    callback: (port: number) => { console.log("Server running on port "+port); },
    port: 3000,
    verbose: true // set to false to disable debug logs
});

Hint: the port and callback are optional arguments, if no port is provided the server tries to read the process from the environmental variables, should this fail the port 3000 is used and the default callback logs the used port to the console.

Decorators

  • @Controller(route: string) Defining a controller allowing using the route decorators to automatically register routes. Note: the controller has to be a class inheriting the BaseController class.

  • @Get(route?: string) - GET method (parameter optional, defaults to method name).

  • @Post(route?: string) - POST method (parameter optional, defaults to method name).

  • @Put(route?: string) - PUT method (parameter optional, defaults to method name).

  • @Delete(route?: string) - DELETE method (parameter optional, defaults to method name).

  • @Middleware Defining a middleware allowing using the middlewareFunction decorators to automatically register middlewares. Note: the Middleware has to be a class inheriting the BaseMiddleware class.

  • @MiddlewareFunction(route?: string) - Define a Middleware function.

Technologies

License

MIT