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

throw-return

v0.0.1

Published

Return using throw

Downloads

3

Readme

throw-return

Return using throw

npm install throw-return

npm Build Status Greenkeeper badge

Throw errors to communicate a return value.

Warning: Evaluate your use cases before using this library. Using error handling to short-circuit functions is slower and more obscure than returning. This library should be used as part of a larger abstraction. Unless that abstraction provides more benefits in itself, go with plain return.

Documentation

throwReturnError

throwReturnError(value: any[, message: String])

Throw an error communicating value as the return value. Optionally give the error a message.

handleReturnError

handleReturnError(func: Function): any

Invoke func and, if a throw-return error is thrown, return the communicated value. If a promise is returned rejecting a throw-error error, the communicated value is resolved.

Example

We have found if (!y) return x too tiresome to write. Let's build an assert(y, x) to save some keystrokes.

Instead of this:

function example () {
  if (!condition1) {
    return value1
  }
  if (!condition2) {
    return value2
  }
  return value3
}

We can do:

function example () {
  assert(condition1, value1)
  assert(condition2, value2)
  return value3
}

If you define assert and control all calls to example:

function assert (condition, value) {
  if (!condition) {
    throwReturnError(value)
  }
}

function run (func) {
  return handleReturnError(func)
}

const value = run(example)