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

prepared

v0.1.1

Published

Prepared callback error handling.

Downloads

1

Readme

prepared NPM version Build Status

Prepared callback error handling.

Have you ever been making a server or something or some async program, like this:

blahBlah(function (err, data) {
  if (err) return response('error happened blah blah')
  // ...
})

fooBarBaz(function (err, data) {
  if (err) return response('error happened blah blah')
  // ...
})

But you end up handling a lot of particular/noisy errors the same way?

This is a super small way of solving that:

var handler = prepared(() => response('internal server error'))

blahBlah(handler(function (data) {
  // ...
}))

fooBarBaz(handler(function (data) {
  // ...
}))

You can make them a bit more dynamic through arguments. Useful for a logging mechanism as well.

Installation

$ npm install --save prepared

Usage

prepared(errorHandler) -> handler

Prepare a Node-style callback with an error handler, so subsequent usage only focuses on data.

Parameters

  • errorHandler (Function): A node-style callback with parameters (err, ...args).

Returns

This only returns handler, another function. See docs below for more details.

Examples

var handler = prepared(function (err) {
  // handle the error...
})

handler(callback)

Create a callback function combined with your prepared error handler.

Parameters

  • callback (Function): A regular callback with no err parameter (already handled).

Returns

This only returns a Node-style callback that is combined with your previous errorHandler.

Examples

// Create `handler` function:
var h = prepared(function (err) {
  console.error('Failed to read file')
})

// Use it as a callback
fs.readFile('./blah.js', h(function (data) {
  // ...
}))

// Reuse again:
fs.readFile('./foo.txt', h(function (data) {
  // ...
}))

Arrow functions

Get slim and good looking code with arrow functions in combination with this module:

// Create `handler` function:
var h = prepared(err => console.error('Failed to read file'))

// Use it as a callback
fs.readFile('./blah.js', h(data => ...))

// Reuse again:
fs.readFile('./foo.txt', h(data => ...))

License

MIT © Jamen Marz