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

@oats-ts/try

v0.0.51

Published

This library wraps the result of a synchronous operation, expressing either a success or a failure.

Downloads

205

Readme

@oats-ts/try

This library wraps the result of a synchronous operation, expressing either a success or a failure.

motivation

In typescript we have no built in way of conveying what errors might a function fail with. This is ok, if you are using errors as a "panic" mechanism, and you don't want to recover. But for libraries, where errors should be well defined, and users should be able to recover from them this is not suitable. The reason this library was created is to support typed errors for oats

basic usage

import { success, failure, isSuccess, Try } from '@oats-ts/try'

function divide(a: number, b: number): Try<number> {
  if (b === 0) {
    return failure([
      {
        message: 'cannot be 0',
        severity: 'error',
        path: 'b',
        type: 'division-by-zero',
      },
    ])
  }
  return success(a / b)
}

const result = divide(1, 2)

// isSuccess and isFailure are type guards, without type narrowing you can't access neither .data nor .issues
if (isSuccess(result)) {
  console.log('divide was successful', result.data)
} else {
  console.log('divide failed', result.issues)
}

utilities

There are some common utility methods exposed that make it easier to work with Trys

fromArray

Creates a Try<T[]> from Try<T>[]. Useful when have a list of tries as a result of Array.map, but you care about the correctness of all results.

import { fromArray } from '@oats-ts/try'

const numbers: number[] = getNumbersFromUser()

const dividedNumbers = fromArray(numbers.map((num) => divide(5, num)))

if (isSuccess(dividedNumbers)) {
  console.log('Here are the results:', dividedNumbers.data)
} else {
  console.log('Some of your inputs are wrong:', dividedNumbers.issues)
}

fromRecord

Creates a Try<Record<A, B>> from Record<A, Try<B>>. Useful when you have an object, where each field is a computed value, and you care about the correctness of each.

import { fromRecord } from '@oats-ts/try'

const resultObject = {
  by5: divide(10, 5),
  by3: divide(10, 3),
  by1: divide(10, 1),
} as const

// result is of type Try<Record<'by5' | 'by3' | 'by1', number>>
const result = fromRecord(resultObject)

zip

Wrapper on top of fromArray, but works with statically typed tuples

import { zip } from '@oats-ts/try'

const divisionResult = divide(5, 3)
const stringResult = success('')

// result is of type Try<[number, string]>
const result = zip(divisionResult, stringResult)

fluent

The fluent method exposes some functional behaviour on the wrapped Try:

const result = fluent(divide(a, b))
  // .map runs performs the given transformation on .data if the Try is a success, otherise delegates the failure
  .map((result) => result - 1)
  // .map runs performs the given transformation on .data if the Try is a success, and carries on with the returned try
  .flatMap((result) => divide(5, result))
  // .get unwraps the Try, you have to provide a callback for both the success and the error case
  .get(
    (data) => data,
    (issues) => NaN,
  )