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

jfq

v1.2.11

Published

JSONata on the command line

Downloads

1,294

Readme

npm test

jfq

JSONata on the command line.

This was inspired by the excellent jq utility, and uses JSONata rather than the jq language.

Installation

npm install --global jfq

Usage

jfq [options] [<JSONata query>] [<files>]

It is good practice to put the JSONata query in single quotes, so that the shell does not attempt to interpret it.

The output will formatted as JSON, unless it's an array of simple objects (e.g. string, number) when the output is flattened to a series of lines, so that it can be piped to another program such as xargs.

Options

  • -n, --ndjson output as newline-delimited JSON (each object on a single line)
  • -j, --json force output as JSON, when it would normally be flattened
  • -y, --yaml output as YAML
  • -a, --accept-yaml accept YAML input
  • -q, --query-file <path> read JSONata query from a file

Examples

  • To read the version of JSONata from the file package.json:
jfq 'dependencies.jsonata' package.json

# ^1.5.0
  • To find out how many downloads of JSONata there have been each month in the past year:
curl -s \
  https://api.npmjs.org/downloads/range/last-year/jsonata \
  | jfq 'downloads{$substring(day, 0, 7): $sum(downloads)}'

# {
#  "2017-02": 36216,
#  "2017-03": 46460,
#  "2017-04": 40336,
#  ...
# }