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

pathington

v2.1.0

Published

Custom identity functions for composability

Readme

pathington

Create or parse an object path based on dot or bracket syntax.

Table of contents

Usage

import { create, parse } from 'pathington';

const parsedPath = parse('some[0].deeply["nested path"]');

console.log(parsed); // ['some', 0, 'deeply', 'nested path']

const createdPath = create(['some', 0, 'deeply', 'nested path']);

console.log(createdPath); // 'some[0].deeply["nested path"]'

Methods

create

create(path: Array<number|string>, quote?: '"' | "'" | '```'): string

Create a path string based on the path values passed.

console.log(create(['simple'])); // 'simple'
console.log(create(['array', 0])); // 'array[0]'
console.log(create(['array', 0, 'with', 'quoted keys'])); // 'array[0].with["quoted keys"]'
console.log(create(['special', '%characters*'])); // 'special["%charactres*"]'

Optionally, you can pass in the quote string to use instead of ". Valid values are backtick or single-quote.

console.log(create(['quoted keys'], "'")); // ['quoted keys']

Symbols

You can provide symbols, and a string path will be created from it:

const symbol = Symbol('foo');
console.log(create(['array', 0, 'with', symbol])); // 'array[0].with[Symbol()]'

This can be used in concert with parse to extract the values pack:

const symbol = Symbol('foo');
const path = create(['array', 0, 'with', symbol]);
const parsedPath = parse(path);
console.log(parsedPath.at(-1) === symbol); // true

Because symbol values cannot be statically analyzed for their value by TS in the same way that numbers or strings can, a consistent visual representation is used for all symbols:

const symbol = Symbol('foo');
const path = create(['array', 0, 'with', symbol]);
console.log(path); // array[0].with[Symbol()]

parse

parse(path: (Array<number|string>|string)): string

Parse a path into an array of path values.

console.log(parse('simple')); // ['simple']
console.log(parse('dot.notation')); // ['dot', 'notation']
console.log(parse('array[0]')); // ['array', 0]
console.log(parse('array[0].with["quoted keys"]')); // ['array', 0, 'with', 'quoted keys']
console.log(parse('special["%characters*"]')); // ['special', '%characters*']
  • If a path string is provided, it will be parsed into an array
  • If an array is provided, it will be mapped with the keys normalized

Symbols

While symbols can be used with this library, parse will only recognize them in a string path when that path is created by create. If you try to manually stringify a symbol, it will identiy that value as a string key when parsing.