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

@cef-ebsi/problem-details-errors

v2.1.2

Published

EBSI API Problem Details Errors library

Downloads

15,570

Readme

EBSI Logo

EBSI API Problem Details Errors Library

Normalize EBSI API errors with Problem Details.

Table of Contents

  1. Installation
  2. Usage
  3. Testing
  4. Licensing

Installation

npm install @cef-ebsi/problem-details-errors

or if you use yarn

yarn add @cef-ebsi/problem-details-errors

Usage

Classes available:

  • ProblemDetailsError: Generic class
  • BadRequestError (400)
  • UnauthorizedError (401)
  • PaymentRequiredError (402)
  • ForbiddenError (403)
  • NotFoundError (404)
  • MethodNotAllowedError (405)
  • NotAcceptableError (406)
  • ProxyAuthenticationRequiredError (407)
  • RequestTimeoutError (408)
  • ConflictError (409)
  • GoneError (410)
  • LengthRequiredError (411)
  • PreconditionFailedError (412)
  • PayloadTooLargeError (413)
  • UriTooLongError (414)
  • UnsupportedMediaTypeError (415)
  • RangeNotSatisfiableError (416)
  • ExpectationFailedError (417)
  • LockedError (423)
  • PreconditionRequiredError (428)
  • TooManyRequestsError (429)
  • InternalServerErrorError (500)
  • NotImplementedError (501)
  • ServiceUnavailableError (503)

Import the class you want to use, e.g.:

import { NotFoundError } from "@cef-ebsi/problem-details-errors";

Then throw a new error:

// Without any params
throw new NotFoundError();
// the Problem Details document looks like this: { title: 'Not Found', status: 404 }

// With a title only
throw new NotFoundError("Record not found");
// -> { title: 'Record not found', status: 404 }

You can also set the different properties of a Problem Details document: "type", "detail" and "instance":

throw new NotFoundError("Record not found.", {
  detail: "Couldn't find any record matching ID 123",
});
// -> { title: 'Record not found.', status: 404, detail: "Couldn't find any record matching ID 123" }

If you want to add custom attributes to the Problem Details error, use options.extensions:

throw new NotFoundError("Record not found.", {
  extensions: {
    "invalid-params": [
      {
        name: "age",
        reason: "must be a positive integer",
      },
      {
        name: "color",
        reason: "must be 'green', 'red' or 'blue'",
      },
    ],
  },
});
// ->
// {
//   title: 'Record not found.',
//   status: 404,
//   'invalid-params': [
//     { name: 'age', reason: 'must be a positive integer' },
//     { name: 'color', reason: "must be 'green', 'red' or 'blue'" }
//   ]
// }

If you want to get the JSON representation of the Error, use the .toJSON() method:

const error = new NotFoundError();
const jsonError = error.toJSON();
// jsonError is now equal to { title: 'Not Found', status: 404 }

If you want the string representation, use the .toString() method:

const error = new NotFoundError();
const stringError = error.toString();
// stringError is now equal to: 404 - Not Found

Testing

Run:

yarn test

Licensing

Copyright (c) 2019 European Commission Licensed under the EUPL, Version 1.2 or - as soon they will be approved by the European Commission - subsequent versions of the EUPL (the "Licence"); You may not use this work except in compliance with the Licence. You may obtain a copy of the Licence at:

Unless required by applicable law or agreed to in writing, software distributed under the Licence is distributed on an "AS IS" basis, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the Licence for the specific language governing permissions and limitations under the Licence.