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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@qnx/errors

v0.8.8

Published

Collection for handle express error response

Readme

@qnx/errors

@qnx/errors provides a set of custom error classes to help you simplify and standardize error handling in your JavaScript/TypeScript applications.

🤖 MCP Server: https://qnx-mcp-server.vercel.app/mcp/errors


📑 Table of Contents

✨ Features

| Feature | Description | | ------- | ----------- | | 🎯 Typed errors | Each scenario has its own class — no guessing what went wrong | | 📦 Consistent shape | Every error produces the same { error, errors } response structure | | ⚙️ Configurable codes | Default HTTP status codes work out of the box, override them if needed | | 🔗 Built for @qnx/response | Errors thrown inside asyncValidatorHandler are caught and formatted automatically |

📦 Installation

npm install @qnx/errors

# yarn
yarn add @qnx/errors

# pnpm
pnpm add @qnx/errors

💡 Usage

All examples below show errors thrown inside asyncValidatorHandler from @qnx/response. The handler catches them and sends the formatted HTTP response automatically.

InvalidValueError

Use when a single field fails validation. Pass the field name as key and a message.

import { asyncValidatorHandler } from '@qnx/response'
import { InvalidValueError } from '@qnx/errors'

router.get('/users/:id', asyncValidatorHandler(async (req) => {
  const user = await User.findById(req.params.id)
  if (!user) throw new InvalidValueError('User not found.', { key: 'id' })
  return user
}))

HTTP 400 response:

{
  "error": "User not found.",
  "errors": {
    "id": ["User not found."]
  }
}

ValidationError

Use when multiple fields fail validation. Build the errors object manually and pass it in.

import { asyncValidatorHandler, initializeApiResponse } from '@qnx/response'
import { ValidationError } from '@qnx/errors'

router.post('/register', asyncValidatorHandler(async (req) => {
  const { email, password } = req.body
  const errors: Record<string, string[]> = {}

  if (!email) errors.email = ['Email is required.']
  if (!password) errors.password = ['Password must be at least 8 characters.']

  if (Object.keys(errors).length) {
    throw new ValidationError('Validation failed', { errRes: { errors } })
  }

  const user = await User.create({ email, password })
  return initializeApiResponse().setData(user).setMessage('Registered.')
}))

HTTP 400 response:

{
  "error": "Validation failed",
  "errors": {
    "email": ["Email is required."],
    "password": ["Password must be at least 8 characters."]
  }
}

UnauthenticatedUserError

Use when a request is missing authentication or the token is invalid.

import { asyncValidatorHandler } from '@qnx/response'
import { UnauthenticatedUserError } from '@qnx/errors'

router.get('/profile', asyncValidatorHandler(async (req) => {
  if (!req.headers.authorization) {
    throw new UnauthenticatedUserError('Authentication required.')
  }
  return await User.findById(req.user.id)
}))

HTTP 401 response:

{
  "error": "Authentication required."
}

ServerError

Use for unexpected failures that the user cannot fix — database down, third-party API unreachable, etc.

import { asyncValidatorHandler } from '@qnx/response'
import { ServerError } from '@qnx/errors'

router.get('/reports', asyncValidatorHandler(async (req) => {
  const result = await ReportService.generate().catch(() => {
    throw new ServerError('Report generation failed. Please try again later.')
  })
  return result
}))

HTTP 500 response:

{
  "error": "Report generation failed. Please try again later."
}

ApiError

The base class — use it when none of the above fit and you need a custom HTTP status code.

import { asyncValidatorHandler } from '@qnx/response'
import { ApiError } from '@qnx/errors'

router.post('/payment', asyncValidatorHandler(async (req) => {
  const result = await PaymentService.charge(req.body)
  if (result.status === 'declined') {
    throw new ApiError('Payment declined.', 402, {
      errRes: { errors: { card: ['Insufficient funds.'] } }
    })
  }
  return result
}))

HTTP 402 response:

{
  "error": "Payment declined.",
  "errors": {
    "card": ["Insufficient funds."]
  }
}

⚙️ Customizing Error Codes

Default HTTP status codes are 400 (validation), 401 (unauthenticated), and 500 (server error). Override them once at app startup with setErrorCodes:

import { setErrorCodes } from '@qnx/errors'

setErrorCodes({
  VALIDATION_ERROR_CODE: 422,
  UNAUTHENTICATED_USER_ERROR_CODE: 403,
  SERVER_ERROR_CODE: 503
})

This affects all ValidationError, InvalidValueError, and UnauthenticatedUserError instances globally.


📘 Error Class Reference

| Class | Constructor | HTTP Code | Use When | | ----- | ----------- | --------- | -------- | | InvalidValueError | (message, { key }) | 400 | A single field is invalid | | ValidationError | (message, { errRes: { errors } }) | 400 | Multiple fields fail validation | | UnauthenticatedUserError | (message) | 401 | Auth token missing or invalid | | ServerError | (message) | 500 | Internal failure the user can't fix | | ApiError | (message, code, { errRes? }) | Custom | Any scenario needing a custom code |

Methods available on all classes

| Method | Returns | Description | | ------ | ------- | ----------- | | .getCode() | number | The HTTP status code | | .getErrorResponse() | ErrorResponse \| undefined | The structured error payload | | .message | string | The error message (from Error) |


🤖 MCP Server

AI tools for this package are available via the QNX MCP Server.

Endpoint: https://qnx-mcp-server.vercel.app/mcp/errors

| Tool | Description | | ---- | ----------- | | get-error-class-docs | Constructor signature, methods, examples, and when to use each error class | | build-api-error | Instantiate an error class with real values — preview resolved code and errorResponse |

Supported clients: Claude Desktop · Claude Code · Cursor · Windsurf · Cline · Continue.dev · Codex CLI · ChatGPT Desktop

HTTP (Streamable HTTP)

{
  "mcpServers": {
    "qnx-errors": {
      "url": "https://qnx-mcp-server.vercel.app/mcp/errors"
    }
  }
}

stdio (via npx)

{
  "mcpServers": {
    "qnx-errors": {
      "command": "npx",
      "args": ["-y", "@qnx/mcp", "errors"]
    }
  }
}

🤝 Contributing

Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change. Please make sure to update tests as appropriate.

📄 License

MIT License © 2023-PRESENT Yatendra Kushwaha