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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@uniresp/errors

v0.1.7

Published

Typed error classes (AppError & subclasses).

Readme

@uniresp/errors

VN (tóm tắt): Tập hợp các error classes đã chuẩn hoá (AppError & các lớp con) để ném lỗi có code, message, details, và status nhất quán.

TypeScript License: MIT

Install

npm i @uniresp/errors
# or
pnpm add @uniresp/errors

What you get

  • AppError: base class → new AppError(code, message, details?, status = 400)
  • UnauthorizedErrorAUTH.UNAUTHORIZED, HTTP 401
  • NotFoundErrorRESOURCE.NOT_FOUND, HTTP 404
  • ValidationErrorINPUT.VALIDATION, HTTP 422
  • SystemErrorSYS.UNKNOWN, HTTP 500

All of these work seamlessly with @uniresp/server-express’s errorHandler to emit the standardized ApiError JSON.

Usage

import { ValidationError, NotFoundError, AppError } from '@uniresp/errors';

// throw from services/handlers
function createUser(input: any) {
  if (!input?.email)
    throw new ValidationError({ field: 'email' }, 'Email is required');
  // ...
}

async function getUser(id: string) {
  const user = await db.user.findById(id);
  if (!user) throw new NotFoundError('User not found');
  return user;
}

// customizing
throw new AppError(
  'PAYMENT.REJECTED',
  'Card declined',
  { reason: 'insufficient_funds' },
  402
);

Error shape produced by adapters

When used with @uniresp/server-express, thrown AppError (or subclasses) are converted to:

{
  "ok": false,
  "error": {
    "code": "INPUT.VALIDATION",
    "message": "Invalid input",
    "details": { "...": "..." },
    "traceId": "req-123"
  }
}

Notes

  • Prefer stable codes (e.g. USER.NOT_FOUND) over free-text parsing.
  • details is optional and can carry validation errors, raw provider payloads, etc.
  • You can extend AppError to add domain-specific errors while keeping consistency.

License

MIT © 2025-present