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

rfc-7807-problem-details

v1.2.0

Published

Typescript implementation of rfc 7807

Downloads

319

Readme

Typescript implementation of RFC 7807 inspired from Hellang ProblemDetails

Install

npm i rfc-7807-problem-details
# Using Yarn
yarn add rfc-7807-problem-details

Problem details options

  • typePrefix - Reference
  • contentTypes - response content type, defaults to "application/problem+json"
  • mapStatusCode - a function that creates default problem details in case there's no mapping for the current error or the predicate mapping didn't pass
  • appendCacheHeaders - a function the add no cache response header
  • includeExceptionDetails - a function that determines whether to include exception details or not.
  • exceptionDetailsPropertyName - the property name that will have the error stack trace, defaults to exceptionDetails

Cache headers

By default these headers will be added

"cache-control": "no-cache, no-store, must-revalidate"
"pragma": "no-cache"
"etag": "0"
"expires": "0"

You can modify this behaviour by changing appendCacheHeaders option

// Default function
options.appendCacheHeaders = (setHeader) => {
	setHeader("cache-control", "no-cache, no-store, must-revalidate");
	setHeader("pragma", "no-cache");
	setHeader("etag", "0");
	setHeader("expires", "0");
};

// Do not add any cache header
options.appendCacheHeaders = (setHeader) => {};

// Add custom cache headers
options.appendCacheHeaders = (setHeader) => {
	setHeader("cache-control", "no-cache, no-store, must-revalidate");
	setHeader("pragma", "no-cache");
	setHeader("etag", "0");
	setHeader("expires", "0");
	setHeader("Last-Modified", "Wed, 21 Oct 2015 07:28:00 GMT"); // This line
};

Framework support

The library support Koa.js and express.js out of the box

  • Express
import express from "express";
import { problemDetailsMiddleware } from "rfc-7807-problem-details";
const app = express();

// Should be added at the last of the middleware chain
app.use(problemDetailsMiddleware.express());

Complete example

  • Koa
import Koa from "koa";
import { problemDetailsMiddleware } from "rfc-7807-problem-details";
const app = new Koa();

// Should be added at the start of the middleware chain
app.use(problemDetailsMiddleware.koa());

Complete example

  • Deno - Oak
import { Application } from "https://deno.land/x/oak/mod.ts";
import {
	ProblemDetailsException,
	ProblemDetailsOptions,
	ProblemDetailsSetup,
} from "https://esm.sh/rfc-7807-problem-details";
const app = new Application();

app.use(async (ctx, next) => {
	// set your options before constructing ProblemDetailsSetup
	const options = new ProblemDetailsOptions();
	options.typePrefix = `https://example.com/probs/out-of-credit`;

	const setup = new ProblemDetailsSetup(options);

	return async (context: any, next: any) => {
		try {
			await next();
		} catch (error) {
			options.appendCacheHeaders((name, value) =>
				ctx.response.headers.set(name, value)
			);

			const problem = setup.prepareProblemDetails(error, context);
			ctx.response.headers.set("content-type", options.contentTypes);
			context.status = problem.status;
			context.body = problem;
		}
	};
});

app.use(async (ctx, next) => {
	switch (ctx.request.url.pathname) {
		case "/example/throw":
			throw new ProblemDetailsException({
				type: "cannot-proceed",
				status: 400,
				title: "You cannot proceed.",
			});
		default:
			ctx.response.body = "Hello World";
			break;
	}
	await next();
});

await app.listen({ port: 8000 });

If you'd like to support custom framework take a look at the source code to see how you can do it.

For more examples check the demo directory.