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

tryit

v1.0.3

Published

Module to wrap try-catch for better performance and cleaner API.

Downloads

1,109,515

Readme

tryit

Tiny module wrapping try/catch in JavaScript.

It's literally 11 lines of code, just read it that's all the documentation you'll need.

install

npm install tryit

usage

What you'd normally do:

try {
    dangerousThing();
} catch (e) {
    console.log('something');
}

With try-it (all it does is wrap try-catch)

var tryit = require('tryit');

tryit(dangerousThing);

You can also handle the error by passing a second function

tryit(dangerousThing, function (e) {
    if (e) {
        console.log('do something');
    }
})

The second function follows error-first pattern common in node. So if you pass a callback it gets called in both cases. But will have an error as the first argument if it fails.

WHAT? WHY DO THIS!?

Primary motivation is having a clean way to wrap things that might fail, where I don't care if it fails. I just want to try it.

This includes stuff like blindly reading/parsing stuff from localStorage in the browser. If it's not there or if parsing it fails, that's fine. But I don't want to leave a bunch of empty catch (e) {} blocks in the code.

Obviously, this is useful any time you're going to attempt to read some unknown data structure.

In addition, my understanding is that it's hard for JS engines to optimize code in try blocks. By actually passing the code to be executed into a re-used try block, we can avoid having to have more than a single try block in our app. Again, this is not a primary motivation, just a potential side benefit.

license

MIT