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

@obisiket1/express-utils

v0.0.86

Published

This is a library of utility decorators, components, and functions that can be used together with typescript express

Downloads

38

Readme

Express Utils

This is an express based utility library that provides utility decorators that can be used together with express typescript.

UseHTTPDecorator

The useHTTPDecorator function is an improvement over the useDecorator. It supports the this variable. The extended class constructor is instantiated within the $register static method that is shipped with the useHTTPDecorator().

Routes can be easily setup using:

import { useHttpDecorator } from "@obisiket1/express-utils";
import { Router } from "express";

const { BaseController, Http, P } = useHttpDecorator();

@Http.Controller()
export default class AuthCtrl extends BaseController(Router) {
  @Http.Get("/api")
  index(@P.Query() query: Record<string, any>) {
    return {
      data: query,
    };
  }
}

That sets up the controller with the route /api, which can then be registered to the express app setup using the mount function.

import { mount } from "@obisiket1/express-utils";
import express from "express";

const app = express();

app.use("/", mount(AuthCtrl))

...

export default app

That also supports for multiple Controllers in the form.

app.use("/v1", mount([
  Controller1,
  Controller2
  ...
  ControllerN
]))

Server

You can also use our Server class to setup the server. The Server class provides the ability to add setup functions to the server. It also provides the graceful shutdown out of the box.

Check out the example below:

import { Server } from "@obisiket1/express-utils";
import app from "./app";

Server.start({
  force: true,
  expressApp: app,
  onStart: ({ port }) => {
    console.log("Server has started @", port);
  },
});

Logger

To set up a logger for a given application use:

const logger = createLogger({
  scope: __filename,
  logDebug: false,
});

CreateConfig

This is a helper function that not only helps to manage configuration but also provides a way to validate the configuration. To use this function use the following:

import { createConfig } from "@obisiket1/express-utils";

export default createConfig({
  config: {
    // configuration goes here
  },
});

Mail

This is still experimental, it provides a way to handle mails on your server; Here's an example:

class Sender implements ISender {
  send(mail: IMail): void {
    console.log("Sent!", mail);
  }
}

const { Mail } = useMailer({
  sender: new Sender(),
  templatePath: path.join(__dirname, "templates"),
});

Mail.create({
  template: "text",
  subject: "Hello",
  data: {
    name: "Treasure",
    first_name: "Obisike",
  }
}).send();

It basically makes your templates readily available using a lightweight template compiler. You can also build your template compiler and add it to the useMailer options.

const { Mail } = useMailer({
  ...,
  templateEngine: new TemplateEngine(),
  ...,
});

The TemplateEngine must implement the ITemplateEngine interface.

Here is the default option:

const defaultOptions = {
  templateEngine: new StringEngine(),
};

UseDecorator

The useDecorator is a function that returns decorators that can be used to setup your routes

import { Logger, useDecorator } from "@obisiket1/express-utils";
import { NextFunction, Request, Response, Router } from "express";

const { GlobalMiddleware, Success, Controller, Post } = useDecorator();

@GlobalMiddleware({ path: "/auth" })
export default class AuthController extends Controller(Router) {
  @Post()
  async register(req: Request, res: Response, next: NextFunction) {
    const result = {
      data: {
        test: "red",
        jesus: ["red", "green", "blue"],
      },
    };

    return Success(res, result);
  }
}

Decorators Contained in the useDecorator include: