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

@badnoodles/eav

v0.0.3

Published

Helper to use an error as value approach in javascript and typescript

Downloads

1

Readme

EAV

Error As Value

eav is a simple helper to follow an error as value approach instead the try/catch native Javascript approach. The implementation is heavily inspired by how errors are treated in Go. Array destructuring is expect to be used as a way to simulate multiple return values.

Why?

The try/catch approach creates an extra layer of scope that is often weird to deal with, making you add extra indentation or use let variables to continue with your logic after the try/catch logic.

Usage

import { eav } from '@badnoodles/eav'

const [v, err] = await eav<string>(() => Promise.resolve("value"))

if (err) {
  console.error(err)
  /**
   * The if + return will enable typescript's type narrowing
   * Comment out the return to see typescript complaining about the type of `v`
   * being possibly null on the console log below
   */
  return
}

console.log(v.endsWith("ue"))

Check the tests for more usage examples.