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

error-http-response

v3.0.0

Published

Create HTTP error responses

Downloads

1,103

Readme

Node Browsers TypeScript Codecov Minified size Mastodon Medium

Create HTTP error responses.

This converts errors to plain objects (RFC 7807, "problem details") to use in an HTTP response.

Hire me

Please reach out if you're looking for a Node.js API or CLI engineer (11 years of experience). Most recently I have been Netlify Build's and Netlify Plugins' technical lead for 2.5 years. I am available for full-time remote positions.

Example

The main HTTP response fields are automatically set using error.name, error.message error.stack and other error properties.

const error = new AuthError('Could not authenticate.')
error.userId = 62
const object = errorHttpResponse(error)
// {
//   title: 'AuthError',
//   detail: 'Could not authenticate.',
//   stack: `AuthError: Could not authenticate.
//     at ...`,
//   extra: { userId: 62 }
// }

Additional fields can be explicitly set in the error class's constructor, using this.http.

class AuthError extends Error {
  constructor(...args) {
    super(...args)
    this.http = {
      type: 'https://example.com/probs/auth',
      status: 401,
    }
  }
}

Or on the error instance, using error.http.

const error = new AuthError('Could not authenticate.')
Object.assign(error.http, {
  instance: '/users/62',
  extra: { userId: 62 },
})

Or as an argument.

import errorHttpResponse from 'error-http-response'

const object = errorHttpResponse(error, {
  extra: { isHttp: true },
})
// {
//   type: 'https://example.com/probs/auth',
//   status: 401,
//   title: 'AuthError',
//   detail: 'Could not authenticate.',
//   instance: '/users/62',
//   stack: `AuthError: Could not authenticate.
//     at ...`,
//   extra: { isHttp: true, userId: 62 },
// }

Install

npm install error-http-response

This package works in both Node.js >=18.18.0 and browsers.

This is an ES module. It must be loaded using an import or import() statement, not require(). If TypeScript is used, it must be configured to output ES modules, not CommonJS.

API

errorHttpResponse(error, options?)

value Error | any
options Options?
Return value: HttpResponse

Converts error to a plain object (RFC 7807, "problem details") to use in an HTTP response.

error should be an Error instance, but invalid errors are automatically normalized.

Options

Type: object

The options and the return value have the same shape (RFC 7807). Options can be passed either as an argument to errorHttpResponse() or be set to error.http.

Options are validated: an exception is thrown if their syntax is invalid.

type

Type: urlString
Default: undefined

URI identifying and documenting the error class. Ideally, each error class should set one.

status

Type: integer
Default: undefined

HTTP status code.

title

Type: string
Default: error.name

Error class name.

detail

Type: string
Default: error.message

Error description.

instance

Type: urlString
Default: undefined

URI identifying the value which errored.

stack

Type: string
Default: error.stack

Error stack trace. Can be set to an empty string.

extra

Type: object
Default: any additional error properties

Additional information. This is always safe to serialize as JSON. Can be set to an empty object.

Related projects

Support

For any question, don't hesitate to submit an issue on GitHub.

Everyone is welcome regardless of personal background. We enforce a Code of conduct in order to promote a positive and inclusive environment.

Contributing

This project was made with ❤️. The simplest way to give back is by starring and sharing it online.

If the documentation is unclear or has a typo, please click on the page's Edit button (pencil icon) and suggest a correction.

If you would like to help us fix a bug or add a new feature, please check our guidelines. Pull requests are welcome!