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

http-problem-details

v0.1.5

Published

HTTP Problem Details according to RFC 7807

Downloads

24,849

Readme

Conventional Commits Join the chat at https://gitter.im/pdmlab/http-problem-details

HTTP Problem Details (RFC 7807) for Node.js

This library implements HTTP Problem details (RFC 7807) for HTTP APIs.

Installation

npm install http-problem-details

or

yarn add http-problem-details

Usage

http-problem-details current supports these options:

  • type (string) - A URI reference [RFC3986] that identifies the problem type.
  • title (string) - A short, human-readable summary of the problem type.
  • status (number) - The HTTP status code ([RFC7231], Section 6) generated by the origin server for this occurrence of the problem. If only status is provided type will be set to about:blank and title will be become the reason phrase as of the HTTP spec, e.g. "Not Found" if status is 404.
  • instance (stringt) - A URI reference that identifies the specific occurrence of the problem.
  • Extension Members - Provide additional information.

type and instance are validated to be valid URIs and will throw errors if not.

Example

To generate this problem+json result

{
    "type": "https://example.com/probs/out-of-credit",
    "title": "You do not have enough credit.",
    "detail": "Your current balance is 30, but that costs 50.",
    "instance": "/account/12345/msgs/abc",
    "status": 400
}

this code is required:

const ProblemDocument = require('http-problem-details').ProblemDocument;

const doc = new ProblemDocument({
  type: 'https://example.com/probs/out-of-credit',
  title: 'You do not have enough credit.',
  detail: 'Your current balance is 30, but that costs 50.',
  instance: '/account/12345/msgs/abc',
  status: 400
});

Example with Extension Members

To generate this problem+json result

{
    "type": "https://example.com/probs/out-of-credit",
    "title": "You do not have enough credit.",
    "balance": 30,
    "accounts": ["/account/12345", "/account/67890"]
}

this code is required:

const ProblemDocument = require('http-problem-details').ProblemDocument;
const ProblemDocumentExtension = require('http-problem-details').ProblemDocumentExtension;

const extension = new ProblemDocumentExtension({
  balance: 30,
  accounts: ['/account/12345', '/account/67890']
});

const doc = new ProblemDocument({
  type: 'https://example.com/probs/out-of-credit',
  title: 'You do not have enough credit.'
}, extension);

Using http-problem-details with express

Usage of http-problem-details is described in express-http-problem-details ( repository | npm).

Running the tests

npm test

TypeScript

http-problem-details is implemented in TypeScript, hence providing typings out of the box.

Want to help?

This project is just getting off the ground and could use some help with cleaning things up and refactoring.

If you want to contribute - we'd love it! Just open an issue to work against so you get full credit for your fork. You can open the issue first so we can discuss and you can work your fork as we go along.

If you see a bug, please be so kind as to show how it's failing, and we'll do our best to get it fixed quickly.

Before sending a PR, please create an issue to introduce your idea and have a reference for your PR.

We're using conventional commits, so please use it for your commits as well.

Also please add tests and make sure to run npm run lint-ts.

License

MIT License

Copyright (c) 2017 - 2019 PDMLab

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.