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

promise-to-respond

v2.0.1

Published

Simple function that converts promise results to an express response

Downloads

5

Readme

promise-to-respond

Simple function to help with consistent responses when using express.

Installation

npm install --save promise-to-respond

Example usage

const respond = require('promise-to-respond')();
const router = require('express').Router();

router.get('/:key', (req, res) =>
  respond(res, Promise.resolve({ some: 'data' })));

Rules

  • A resolved promise with a defined or null result responds with 200
  • A resolved promise with an undefined result responds with 204
  • A rejected promise with an array responds with 400
  • A rejected promise with an undefined result responds with 404
  • A rejected promise with anything else responds with 500 and a body like this: { error }

Options

{
  toJSON: result => {
    return (typeof (result || {}).toJSON === 'function') ? result.toJSON() : result;
  },
  fieldsToOmit: null
}

toJSON

You can specify a toJSON function that will be called in the case of any response (that is not undefined) to transform the response body as required. It will be called for success responses (200) as well as error responses (400, 500). It can return a Promise or JSON.

const respond = require('promise-to-respond')({
  toJSON: obj => new Promise((resolve, reject) => {
    //TODO convert obj to something else and return the result
  }),
});

The default implementation checks for a toJSON function on the object and uses that if it exists.

fieldsToOmit

You can specify fields to be omitted from the response. This applies the omit function to all array items if the response is an array

const respond = require('promise-to-respond')({
  fieldsToOmit: ['_id', '__v']
});