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

2json

v0.2.1

Published

json flattener that outputs lines similar to xml2

Downloads

44

Readme

json2

simple utility for transforming json documents into grep-able and sed-able lines

install

# json2 was already taken
npm install -g 2json

usage

# json2 args
json2 [file] [< or_file]

# 2json
# -p flag pretty prints json
2json [file] [< or_file] [-p --pretty]

# get package name
basename $(json2 package.json | grep '/name')

# change package name and reconvert lines to json using 2json
json2 < package.json | sed 's@\(/name\)/.*@\1/new-name@' | 2json -p

escapes for json2/2json

The following are escaped--by being in quote strings, as per rules:

  • all forward slashes (/)
  • all index brackets ([ or ])
  • all strings that are just number characters (e.g. 00193425)

You must escape double quotes in strings, json2 does this.

backslash escapes for 2json

The following characters must be escaped to handle issues with newlines using backslashes, whether in quotes or not:

\ <- escape as \\
\n
\r
\f

notes

/ [ ] are reserved by the json line grammar, if such values are found in your json, they will be quoted in double quotes.