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

opres

v2.6.0

Published

Rust-inspired Result object for more elegant success and failure handling

Downloads

11

Readme

opres - Operation Result

Rust-inspired std::result object for JavaScript.

Usage

The idea is to return OperationResult objects from places where you expect failures - database calls, file I/O, remote APIs and so on. OperationResult encapsulates success of the operation, any data returned, and any errors that occurred along the way, allowing you to cleanly write your failure-handling logic on top.

const { OperationResult } = require('opres');

const goodApiCall = () => {
  return new OperationResult('my returned data');
}

const badApiCall = () => {
  return new OperationResult(null, new Error('something went wrong'));
}

// later on in your calling code somewhere
const res1 = goodApiCall();

if (res1.ok) {
  console.log(res1.data);
} else {
  console.error(res1.error);
}

// You can also cause errors to throw using `expect()`.  In this case an error would throw.
const res2 = badApiCall().expect('could not call API');
// However, `expect()` is a no-op for successful operations:
const res3 = goodApiCall().expect('this will not throw');

You can also wrap a series of OperationResults as follows:

const { OperationResult } = require('opres');

const myFirstResult = new OperationResult();
const mySecondResult = new OperationResult();


const myOverallResult = OperationResult.wrap([myFirstResult, mySecondResult]);

Other notes

Pattern matching

JavaScript can't really do any of the nice pattern matching stuff that Rust can do so that's not supported.

The closest you can get is an if statement as seen above:

if (res.ok) {
  // successful
} else {
  // not
}

You'll probably recognise the fetch-style .ok.

Contributions

Pull requests are welcome.

Thanks

If this is useful for you let me know!