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

nullsy

v1.1.2

Published

Tools for testing against null and undefined values.

Downloads

9

Readme

nullsy

Overview

This package includes every tool you need for testing against null or undefined variable.

Usage

Quick Examples

Let's say you have just recieved and parsed server response. You expect the response's structure to be something like this:

const response = {
    go: {
        deep: {
            into: {
                path: 'to success'
            }
        },
        into: {
            not: 'here'
        }
    },
    path: 'not even here'
};

and want to know the value of response.go.deep.into.path.

Of course you can do

if (response && response.go && response.go.deep && response.go.deep.into && response.go.deep.into.path) {
    // ...do amazing stuff
}

but I found out that this approach is rather long.

Using isValidChain in this package, you can simply do

if (isValidChain(response, 'go.deep.into.path')) {
    // ...do even more amazier stuff
}

There are also basic null and/or undefined checkers available just in case you are too awesome to write &&.

isNull(null); // true
isNull(undefined); // false

isUndefined(null); // false
isUndefined(undefined); // true

isNullsy(null); // true
isNullsy(undefined); // true

isValid(someValue) === !isNullsy(someValue); // true

// ...etc

Notable Exceptions

Consider the following object.

const exceptions = {
    path: {
        to: {
            validFalse: false,
            validNull: null,
            validUndefined: undefined
        }
    }
}

Because the actual intended values for exceptions.path.to.validFalse and exceptions.path.to.validNull are indeed false and null, isValidChain call to these value will return true.

However, in the case of exceptions.path.to.validUndefined, the code's intended value is undefined but isValidChain will return false, for it is almost* indistinguishable from not assgining any value to at all and writing that way is often highly discouraged. If you need a value to be left undetermined, use null instead.

* If you really want to assign a value undefined and check if it exists, use Object.keys, Object.getOwnPropertyNames, or Object.getOwnPrpertySymbols, depending on how you assigned it, to find if the key exists.

PoC