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 🙏

© 2026 – Pkg Stats / Ryan Hefner

pth

v1.0.0

Published

Dotting into objects

Readme

pth - What

This is a simple helper for selectors in a React Redux environment. It simplifies the act of creating a function that pics out certain parts of your state depending on the arguments passed in.

At its simplest, you can compare these two functions:

// raw js
const getNameById = (state, id) => {
    const user = state.users[id]
    return user && user.name
}

// pth
const getNameById = pth('$0.users.$1.name')

So pth returns a function that takes an arbitrary number of arguments and attempts to access the property you are looking for. If it fails, it returns undefined.

Of course you can also use it to create small utility functions for accessing properties on objects:

const getFirstName = pth('$0.firstName')
const getLastName = pth('$0.lastName')
// etc...

options argument

pth also takes an options object as second parameter, where you can change a few things:

// If name isn't found, return 'Mr Nobody'
const getNameById = pth('$0.users.$1.name', {or: 'Mr Nobody'})

// Change the identifier from $ to %
const getNameById = pth('%0.users.%1.name', {identifier: '%'})

// Change the splitter from . to ->
const getNameById = pth('%0->users->%1->name', {splitter: '->'})

pth.fromObject

There is a second version where the returned function only takes two arguments:

  1. the object where we expect to find the data we are looking for, and
  2. an object with the keys we need

The path string we pass to it also looks a little different (better if you ask me).

These two are equevalent:

// raw js
const getNameById = (state, {id}) => {
    const user = state.users[id]
    return user && user.name
}

// pth
const getNameById = pth.fromObject('users.$id.name')

This version takes the same options object as second parameter as the above.

Because too much magic?

If giving pth a string is too much magic for you, then know that it also takes an array.

const getNameById = pth(['$0', 'users', '$1', 'name'])

const getNameById = pth.fromObject(['users', '$id', 'name'])

Tiny caution

I don't recommend "building" the function every time you call it. That is, this is probably not a great idea:

const getName = user => pth('$0.name')(user)

The reason is performance. It's not that it is particularly slow; but it is splitting up a string and looping through each of the sections every time; so really it's better to just build the function ahead of time.