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

@yeliex/problem-details

v1.4.1

Published

Problem Details for HTTP APIs (RFC 9457) core implementation

Readme

@yeliex/problem-details

Framework-agnostic RFC 9457 Problem Details core.

Install

pnpm add @yeliex/problem-details

API

ProblemDetail

class ProblemDetail extends Error {
  constructor(status: number, options?: ProblemDetailInit)
  constructor(status: number, detail?: string, options?: ProblemDetailInit)
}
  • status: HTTP status code.
  • detail: optional human-readable detail.
  • options supports standard fields and custom extensions:
    • type (default: about:blank)
    • title (default: HTTP status phrase)
    • instance
    • cause
    • any custom extension members (for example traceId, code, foo)
    • supports Symbol extension members for internal-only metadata
    • extension members with undefined value are ignored in instance assignment

Usage

import { ProblemDetail } from '@yeliex/problem-details';

const problem = new ProblemDetail(404, 'User not found', {
  type: 'https://example.com/problems/user-not-found',
  instance: '/users/42',
  traceId: 'req-123',
});

console.log(problem.toJSON());

Debug Output

ProblemDetail provides custom toString() and Node.js inspect output, which is useful in logs and debugging.

HTTP Error Constructors

http-error is provided as a subpath export (not from root entry):

import { createError, createHttpError, httpErrors } from '@yeliex/problem-details/http-error';

throw new httpErrors.NotFound('User not found');
throw new httpErrors[404]('User not found');
throw new httpErrors['404']('User not found');

const ValidationError = createError(400, 'ValidationError', {
  title: 'Validation Failed',
  type: 'https://example.com/problems/validation-error',
  code: 'VALIDATION_ERROR',
});

const ConflictError = createHttpError(409, 'Conflict detected', {
  title: 'Business Conflict',
  code: 'BUSINESS_CONFLICT',
});

createError overloads:

createError(status: number, name: string)
createError(status: number, name: string, defaultOptions?: ProblemDetailInit)
createError(status: number, name: string, defaultDetail?: string, defaultOptions?: ProblemDetailInit)

createHttpError uses the same default argument model without the explicit name parameter.

Default options are applied first, and instance-time arguments override them:

const ValidationError = createError(400, 'ValidationError', {
  title: 'Validation Failed',
  type: 'https://example.com/problems/validation-error',
  code: 'VALIDATION_ERROR',
});

new ValidationError({ field: 'email' });
new ValidationError('Email is invalid', { field: 'email' });
new ValidationError(undefined, { title: 'Invalid Request' });

JSON Output

problem.toJSON() returns RFC 9457 base fields plus extensions:

{
  "type": "about:blank",
  "title": "Bad Request",
  "status": 400,
  "detail": "Invalid input",
  "instance": "/users",
  "traceId": "req-123"
}

License

MIT