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

questionmark

v1.0.3

Published

A tiny and mighty utility for optional chaining in pure JavaScript

Downloads

3

Readme

questionmark.js

A tiny and mighty utility for optional chaining in pure JavaScript.

# get it 
npm install questionmark
const q = require('questionmark');

// If data.foo.bar.baz[0].bat[10] exists, its value will be returned.
// If any of bar, baz, baz[0], or bat[10] don't exist, we return undefined.
// You don't have to worry about accessing properties on null/undefined anymore!
data.q(q => q.foo.bar.baz[0].bat[10]);

// Not sure if `data` itself is null or undefined? No problem. 
// Use this alternative syntax:
q(data, q => q.foo.bar.baz[0].bat[10]);

// q works with function invocations as well:
data.q(q => q.doSomethingGreat().result);

It's similar to idx.macro but doesn't get babel involved.

Tests

Lovingly tested in mocha.

npm test

Contribute

Fork and PR please.

Background: What is optional chaining?

Imagine you are accessing a property from a deeply nested JSON object (perhaps from a server response?)

fetch("https://www.example.com/api/libraryDb")
    .then(res => res.json())
    .then(json => {        
        let book = json
            .libraries["UL London"].shelves["Science Fiction"]
            .authors["Herbert, Frank"].mostPopularBook.title;
        $("#book-of-the-month")
            .text("The book of the month is: " + book);
    });

But if json, or json.libraries, or json.libraries["UL London"], or any other value in that chain is null or undefined, your callback will throw an exception. You have to write some verbose guard clauses against that:

    let book = !!json && !!json.libraries
        && !!json.libraries["UL London"]
        && !!json.libraries["UL London"].shelves
        && !!json.libraries["UL London"].shelves["Science Fiction"]
        && !!json.libraries["UL London"].shelves["Science Fiction"].authors
        && !!json.libraries["UL London"].shelves["Science Fiction"].authors["Herbert, Frank"]
        && !!json.libraries["UL London"].shelves["Science Fiction"].authors["Herbert, Frank"].mostPopularBook
        && json.libraries["UL London"].shelves["Science Fiction"].authors["Herbert, Frank"].mostPopularBook.title
        || "unknown";

Eugh!

Some languages have optional chaining to indicate that you only want to access a property if it exists; if not, further drill-downs just give you a null value. This way you don't have to test every single step in the chain, and can just check whether you have a real value at the end.

This is also proposed for JavaScript:

    let book = json?.libraries?["UL London"]?
        .shelves?["Science Fiction"]?
        .authors?["Herbert, Frank"]?
        .mostPopularBook?.title || "unknown"

That's much better. questionmark.js aims to tide us over while we wait.

    let book = json.q(q => 
        q.libraries["UL London"].shelves["Science Fiction"]
        .authors["Herbert, Frank"].mostPopularBook.title) 
    || "unknown";