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

http2human

v1.0.1

Published

http2human tries to translate http errors for human use. It wraps `fetch` promises and returns standardized errors.

Downloads

5

Readme

http2human

http2human tries to translate http errors for human use. It wraps fetch promises and returns standardized errors.

When a request to your server from a device actually succeeds, it's nothing short of a small miracle. When it doesn't, a generic error message is dehumanizing to the person attempting to use your service.

Minimal example:

http2human('https://google.com').then(function(body) {
  // do something with your successful response.
  // `body` will be an object if it's JSON parsable,
  // otherwise it'll be a string
}).catch(function(err) {
  alert(err.suggestion);
})

Maximal example:

http2human('https://mycoolserver.com/login', {
  method: 'POST',
  headers: { 'Content-Type': 'application/json' },
  body: { username: 'neil', password: 'nope' }
}).then(function(bodyObjectOrString) {
  // do something with your successful response
}).catch(function(err) {
  switch(err.name) {
   case 'NetworkError':
     console.error(err, err.stack);
     return alert("You might not be connected to the internet. Please check your connection and try again.");
   case 'ServerError':
     console.error(err, err.stack);
     if( err.suggestion ) { return alert(suggestion); }
     if( err.statusCode == 504 ) { return alert("Sorry, our server is backed up. Please try again later."); }
     if( err.responseBody ) { console.error(err.responseBody); }
     return alert("Sorry, something went wrong on our end. Please try again or email [email protected].");
   case 'UserError':
     if( err.suggestion ) { return alert(suggestion); }
     if( err.statusCode == 403 ) { return alert("Your username or password is incorrect") }
     if( err.responseBody && err.responseBody.retriesRemaining ) { return alert(`You have ${err.responseBody.retriesRemaining}`); }
     return alert("Hmm, something's wrong with your last request but we can't tell exactly what it is. Please check your information and try resubmitting or email [email protected]")
   case 'LowLevelError':
   default:
     return alert("Whoa, something went wrong that should not have gone wrong. Please let us know what happened at [email protected]")
  }
})

http2human will not work with all APIs. it assumes:

  1. API responses are in JSON or plaintext
  2. 5xx responses strictly indicate an unexpected server side error.
  3. 4xx responses strictly indicate a user error that should be resolvable by the human on the other side.

In order to populate err.suggestion, the format of an error message suggesting foo must be one of the following:

{
  "error": {
    "message": "foo"
  }
}
{
  "message": "foo"
}
{
  "error": "foo"
}
foo

fetch is a new standard available in modern browsers and react native. If fetch is not available in your environment, http2human will use https://github.com/bitinn/node-fetch