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

nothrow

v1.0.1

Published

Encapsulates typesafe deep object/array access

Downloads

15

Readme

nothrow

Encapsulates typesafe deep object/array access.

The nothrow-mentality is based on the fact, that any kind of input (data which is not created from our application) should be considered evil. 99% of the time the interface might be compatible to a naive implementation, but there is remaining risk of our application to terminate unexpectedly.

    // evil
    configService.setName(uncheckedServerData.configuration.name);

    // better, but boilerplate code
    configService.setName(
        uncheckedServerData
        && uncheckedServerData.configuration
        && uncheckedServerData.configuration.name
    );
    
    // nothrow approach
    configService.setName(nothrow(() => uncheckedServerData.configuration.name));

Accessing deep structures problem

Expect that our application state has an array with persons and we want the name of the first person. We could write

    return state.persons[0].name;

and run into danger that either the array is empty and there is no first person

Uncaught TypeError: Cannot read property 'name' of undefined

or the person array has not yet been initialized

Uncaught TypeError: Cannot read property '0' of undefined

or there is actually no state at all

Uncaught TypeError: Cannot read property 'peoples' of undefined

which forces us to write complex checks as conditional access

    return state && state.persons && state.persons[0] && state.persons[0].name;

or 'early return'

    if(!state)
        return undefined;
    
    if(!state.persons)
        return undefined;
    
    if(!state.persons[0])
        return undefined;
    
    return state.persons[0].name;

(other) Solutions

lodash's get function?

    return _.get(state, 'persons[0].name');

Works, but

  1. typesafetyness is gone
  2. refactoring impossible

the nothrow way

We access structures via accessor function and nothrow guarantees that no exception is thrown, no matter if you're accessing null or undefined via index or calling any non-existing functions.

    import {nothrow} from 'nothrow';
    
    // returns undefined
    return nothrow(() => state.people[0].name);