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

json-pick

v0.1.1

Published

pick(path, matcher)(data): pick values from JSON

Downloads

156

Readme

pick(path, matcher)(data) : pick values from JSON

var person = {
  "name" : "John",
  "age" : 32,
  "kids" : [
    { "name" : "Adam", "age" : 10 },
    { "name" : "Emily", "age" : 7 }
  ],
  "relationships" : [
    { "status" : "ongoing", "with" : { "name" : "Susan" } },
    { "status" : "ended", "with" : { "name" : "Katie" } }
  ]
};

// ----- path extraction

pick("/")(person)              // => person
pick("/name")(person)          // => "John"
pick("/kids[0]/name")(person)  // => "Adam"
pick("/kids[]/name")(person)   // => ["Adam", "Emily"]

// ----- matching

pick("/relationships[*]/with/name", { "/../../status" : "ongoing" })(person)
// => "Susan"

pick("/kids[*]", { "/name" : "Adam" })(person)
// => { "name" : "Adam", "age" : 10 }

Idea

  • pick(path, matcher)(value) maps value to path and returns the result if matcher accepts it

  • path can be thought of as a mapper that maps value as another value selection

  • matcher can be thought of as a filter that filters the selection

Paths

Paths are defined as /-separated selectors, where each selector maps the current selection to another value:

| Selector | Maps to | Example | -------------------- | --------------------- | ---------------------------- | (empty) | current | | field | current[field] | /name for John maps to "John" | [idx] | current[idx] | /kids[0]/name for John maps to John's first kid's name, "Adam" | .. | parent | /../../status (relative to strings "Susan" and "Katie" in the example)

For convenience, field and index-style selectors can be combined in single path segment (i.e. /array[0] instead of /array/[0].

Wildcard matching

When using [idx] selector, instead of using an numerical index, you can specify a wildcard index using [\*].

This will select the first such value in current selection where the rest of the path can be selected. I.e. /kids[\*]/name would select "Adam" because "Adam" is the first kid object with a name attribute.

Wildcard matching can be used together with custom matchers to create find-style queries.

Any matching

You can also omit the index altogether and use [] matcher to filter values in current selection down to those for which the rest of the path can be selected.

/kids[]/name will thus return an array of ["Adam", "Emily"] because both kid objects contain a name attribute.

Any matching can also be used with custom matchers to create filter-style queries.