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 🙏

© 2025 – Pkg Stats / Ryan Hefner

eckspress

v0.3.0

Published

Another approach to using express

Downloads

20

Readme

eckspress

Just a way to use middlewares with contexts with nice typescript type inference.

Example

An example usage, for what is currently implemented, could be something like this:

import { Request, Response, Router } from 'express';
import { BadRequest, Endpoint, Success } from 'eckspress';

const router = Router();
export default router;

// each type of response has a static method for adding logging for example
// note that the status code is already set before this is called
BadRequest.Handler = async (req, res, body, extra) => {
    console.log('BAD REQUEST', JSON.stringify(extra));
};

// a really simple middleware
async function paramID(req: Request, res: Response) {
    if (isNaN(+req.params.id)) {
        // automatically handles response
        return new BadRequest('invalid id, must be number', {
            params: req.params.id,
        });
    }
    return { id: +req.params.id };
}

router.get(
    '/:id',
    Endpoint([paramID], async (context, req, res) => {
        return new Success(`Requested id ${context.id}`);

        // you can also manually handle the response by returning the express.Response instance:
        // return res.status(200).send(``);
    }),
);

Your context parameter in the handler would automatically tell you what the middlewares provide you with.

When a middleware returns a BadResult (like BadRequest), no further middlewares not handler are called, and an apropriate response will automatically be sent back.

With a middleware being able to return an error and stop the chain flow, easily you can implement an authorization middleware.