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

jsend-utils

v3.0.5

Published

Simple helper functions for producing JSend objects and responses.

Downloads

26

Readme

JSend Utils

Simple helper functions for producing JSend objects and responses.

It's important to mention that this implementation differs from the JSend spec in the naming of errors. The spec uses the term fail for a problem with the submitted data or an unsatisfied precondition. It used the term error for a server-side error. I think their terminology is backwards--the caller can correct an error, but not a failure. So, in this implementation, the status field will be error for client errors, and fail for server-side failures.

Installation

Install this module in the usual way:

npm install jsend-utils
    

Usage

To decorate Express's response with methods you can use to return JSend responses, do the following (you'll only need to do this once, typically in your main app.js):

require('./lib/jsend').decorateExpressResponse(require('express').response);
    

Sometimes it's useful for server-side code to return an error to another server-side caller, but provide more details about what went wrong, and do so in the JSend format, making it easier to return a JSend response to the client side. The four Error subclasses provided by this module are intended for that use case.

For full documentation, generate the JSDocs:

npm run-script api-docs

You'll find the generated docs in the out directory.