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

better-try-catch

v0.6.2

Published

Try-catch wrapper for easy error handling.

Downloads

98

Readme

better-try-catch

npm version Build Status Dependency Status Coverage Status

Try-catch wrapper for easy error handling. Inspired by await-to-js.

Installation

$ npm install better-try-catch

Usage

var btc = require('better-try-catch')

var [err, result] = btc(someFunction)(arg1, arg2)
if (!err) {
  // ...
}

// You can also use better-try-catch with async/await functions
async function example1() {
  var [err, result] = await btc(someFunctionThatReturnsPromise)(arg1, arg2)
  if (!err) {
    // ...
  }
}

// Or even use with functions that accept node-style callback:
async function example2() {
  var [err, result] = await btc.promisify(fs.readFile)('data.json', 'utf8')
}

I didn't see it's "better?"

Consider a situation like this:

try {
  doSomething()
} catch (err) {
  // The varaible `err` is only visible in the catch block
}
// With the code goes here, the variable `err` is no longer existing
// If we have to make sure there wasn't anything went wrong above
// How do we know that?
if (!err) {
  // ...
}

Humm, it should be not too hard to solve. After one or three minutes of thinking, we have the code rearranged to be like this:

var err // Hoist the error variable declaration
try {
  doSomething()
} catch (ex) {
  err = ex // Note here
  // Also, we can not simply place the `if` statement inside the catch block
  // Since if no errors occured then the `if` statement will not execute at all
}
// Alright, this time we are able to safely access the error variable outside the try-catch block
if (!err) {
  // ...
}

Okay, seems the problem has gone, with the only exception that the code looks a little more messy now. C'mon! Can't we do it better? better-try-catch to the rescue™!

var btc = require('better-try-catch')
// better-try-catch wraps the function and will catch errors for you
// The wrapped function will *always* return both error and value
// Which somewhat looks like the node-style callbacks
var [err, result] = btc(doSomething)()
// And that's all we have to do, as simple as you can see
if (!err) { // Was there anything went wrong?
  // Nope, we are perfectly sure that everthing is running well as expected! :D
}

License

MIT License, Copyright (c) 2017 Riophae Lee