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

@conjurelabs/err

v1.0.1

Published

Extending the native error constructor

Downloads

2

Readme

Errors

CircleCI

Extending native errors, to give a little more context.

This is useful for differentiating between server (5xx) and user (4xx) errors. As well as making sure internal vs. public-facing error messages are different.

Install

npm install --save @conjurelabs/err

Usage

const { ConjureError } = require('@conjurelabs/err')

throw new ConjureError('something happened')

Public-Facing Errors

Internal error dialogs may not be appropriate for end users. Default 'public' errors are set on every Conjure error.

const { NotFoundError } = require('@conjurelabs/err')

const err = new NotFoundError('sensitive message')

console.log(err.message) // 'sensitive message'

console.log(err.publicMessage) // 'A needed resource was not found'

This can be used to pass back non-sensitive errors to the client, while still logging actual error messages internally.

// in a final express route handler
server.use((err, req, res, next) => {
  if (!err) {
    return next()
  }

  console.log(err) // will log true error message & stack trace

  if (err instanceof ConjureError) {
    return res.status(err.httpStatusCode).send({ message: err.publicMessage })
  }

  // if a native (non ConjureError), then 500
  res.status(500).send({ message: 'An error occurred '})
})

You can signal that a set error message is okay for public users, by passing public: true in an options argument.

const err = new NotFoundError('The file you have requested is not present', { public: true })

This will set .publicMessage to 'The file you have requested is not present'

HTTP Status Codes

Similar to 'public' errors, you may also want to know what http status code an error should associate to.

const { PermissionsError } = require('@conjurelabs/err')

const err = new PermissionsError(`User doesn't have access`)

console.log(err.httpStatusCode) // 403

Wrapping a Native Error

If you want to extend a native error, you can pass in the entire err instance.

const { PermissionsError } = require('@conjurelabs/err')

try {
  await checkPermissions()
} catch(err) {
  throw new PermissionsError(err)
}

Tests

npm test
npm run lint