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

@http4t/result

v0.4.119

Published

A standard way of representing success/failure results, where in the case of failure we might want to flag issues with multiple elements in a complex data structure.

Downloads

5

Readme

@http4t/result

A standard way of representing success/failure results, where in the case of failure we might want to flag issues with multiple elements in a complex data structure.

Basics

A success looks like:

const result = success("this value was ok!");
// -> {value: "this value was ok!"}

A failure looks like:

type Thing = {
  name: string;
  price: number;
}

function validate(value: any) : Result<Thing> {
  const problems = [];

  if(typeof value.name !== 'string')
    problems.push(problem("expected a string", ["name"]))

  if(typeof value.price !== 'number')
    problems.push(problem("expected a number", ["price"]))
  
  if(problems.length > 0) return failure(problems);

  return success(value);
}

validate({});

// -> {problems: [
//          {message: "expected a string", path: ["name"]},
//          {message: "expected a number", path: ["price"]}
//     ]}

Paths

The path in each problem is an array of string | number, which is a subset of jsonpath- just object keys and array indexes.

In the following data structure the value at path ["a", "b", 0, "c"] is 1:

{a: {
  b: [
    {c:1}, 
    {c:2}
  ]
}}

The equivalent json path of ["a", "b", 0, "c"] would be $.a.b.[0].c.

ResultError

Also provided is an error class that plays nicely with test runners and ides.

The error class will calculate an error.expected which is a copy of actual, but with the faulty values replaced with the message of any problems.

const actual = {ok: "ok", wrong: "wrong"};
const error = new ResultError(actual, failure("some error message", ["wrong"]));

console.log(error.expected);
// --> {ok: "ok", wrong: "some error message"}