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

problem-response

v1.0.0

Published

RFC 9457 Problem Details for HTTP APIs — framework-agnostic, TypeScript-first error responses

Readme

problem-response

RFC 9457 Problem Details for HTTP APIs — framework-agnostic, TypeScript-first error responses

Install

npm install problem-response

Usage

import {ProblemDetail, toResponse, notFound, badRequest} from 'problem-response';

// Using factory functions
const problem = notFound('The requested user was not found.');
console.log(problem.toJSON());
// => {type: 'about:blank', title: 'Not Found', status: 404, detail: 'The requested user was not found.'}

// Using the constructor directly
const detailed = new ProblemDetail({
	type: 'https://api.example.com/problems/out-of-credit',
	title: 'You do not have enough credit.',
	status: 403,
	detail: 'Your current balance is 30, but that costs 50.',
	instance: '/account/12345/msgs/abc',
	balance: 30,
	accounts: ['/account/12345', '/account/67890'],
});

// Convert to HTTP response
const response = toResponse(detailed);
// => {status: 403, headers: {'content-type': 'application/problem+json'}, body: '...'}

API

new ProblemDetail(options)

Creates a new ProblemDetail instance that extends Error.

options

Type: object

type

Type: string
Default: 'about:blank'

A URI reference that identifies the problem type.

title

Type: string

A short, human-readable summary of the problem type. Defaults to the standard title for the given status code.

status

Type: number (required)

The HTTP status code for this problem.

detail

Type: string

A human-readable explanation specific to this occurrence of the problem.

instance

Type: string

A URI reference that identifies the specific occurrence of the problem.

Extension members

Any additional properties are treated as extension members per RFC 9457.

.toJSON()

Returns an RFC 9457 compliant plain object.

toResponse(problem)

Returns an HTTP response object with status, headers, and body.

isProblemDetail(value)

Type guard that returns true if the value is a ProblemDetail instance.

Factory functions

  • badRequest(detail?, extensions?) — status 400
  • unauthorized(detail?, extensions?) — status 401
  • forbidden(detail?, extensions?) — status 403
  • notFound(detail?, extensions?) — status 404
  • conflict(detail?, extensions?) — status 409
  • unprocessableEntity(detail?, extensions?) — status 422
  • internalServerError(detail?, extensions?) — status 500

Related

  • RFC 9457 — Problem Details for HTTP APIs

License

MIT