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 🙏

© 2026 – Pkg Stats / Ryan Hefner

controlli

v1.1.5

Published

A handler layer for Express API controllers. Helping out with response/error and param handling.

Readme

Controlli

A handler layer for Express API controllers. Helping out with response/error and param handling.

Sections

Install

npm i controlli

Usage

HandleResponse

HandleResponse is a wrapper function to toss in your controller logic and subsequent service/repository/data provider/etc logic into. It handle sending back correct responses and their status codes.

By using the models stated in the secion above, or just a generic JS error, the responses sent from your api will follow:

  • resolve(data) => statusCode: 200, { data: data }
  • throw ArgumentNullError => statusCode: 400, { err: <error.toString>, data: null }
  • throw ArgumentError => statusCode: 400, { err: <error.toString>, data: null }
  • throw NotFoundError => statusCode: 404, { err: <error.toString>, data: null }
  • throw Error => statusCode: 500, { err: <error.toString>, data: null }
public exampleControllerEndpoint(req: Request, res: Response) {
    HandleResponse(res, new Promise((resolve, reject) => {
     
        // Controller logic/Service call/etc...
        
        // throw Errors if needed
        // OR
        // resolve('data to return in response');
    }));
}

HandleQueryParams

HandleQueryParams is a function to help handle your controller query params. Express has your query params come in as strings, this function will transform them into their type'd counter part.

Ex: "10" => 10, "true" => true

If your params are expected to be booleans or numbers and are not, it will throw the associated Error.

BONUS: If you are using Controlli's HandleResponse() with this functionality, the error response will all be handled by itself, no need for you to be involved.

// NOTE: Written in Typescript
public exampleControllerEndpoint(req: Request, res: Response) {
    HandleResponse(res, new Promise((resolve, reject) => {
        let params = HandleQueryParams(
            req,    // Controller Request
            {       // Give your expected/optional query
                requiredStrings?: string[],
                requiredBooleans?: string[],
                requiredNumbers?: string[],
                optionalBooleans?: string[],
                optionalNumbers?: string[],
            }
        );
        
        // Controller logic/Service call/etc...
        
        resolve('Sucess');
    }));
}

Example

// req.query = { 'reqStr': 'fake-string', 'reqBool': 'true', 'reqNum': '10' }
let params = HandleQueryParams(
    req,
    {
        requiredStrings: ['reqStr'],
        requiredBooleans: ['reqBool'],
        requiredNumbers: ['reqNum'],
        optionalBooleans: ['optBool'],
        optionalNumbers: ['optNum'],
    }
);

console.log(params);
/**
params = {
    reqStr: 'fake-string',
    reqBool: true,
    reqInt: 10
} 
* optBool and optInt will be here if present in req.query
*/

Error Models

Controlli introduces some models to help with error and response handling.

  • ArgumentNullError
  • ArgumentError
  • NotFoundError

You are able to throw these errors at any point in the code. As long as they are not caught in your code, Controlli will handle an error response for you.

Example Project Using Controlli

I setup a starter Typescript Express API project that uses Controlli's functionality.

Check it out here: https://github.com/lukegeiken4/express-typescript-starter

License

The MIT License (MIT)

Copyright (c) 2019 Luke Geiken

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.