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

spod

v1.0.1

Published

a little cli for spitting out data about a flat directory containing some json and markdown.

Readme

spod (spit out data)

a little cli for spitting out data about a flat directory containing some json and markdown.

npm i spod -g

example

take a directory of directories

/example
  /an-entry-name
    - data.json
    - text.md
  /another-one
    - data.json
    - text.md
    - image.jpg

and output a json file to the root directory

/example
  /an-entry-name
  /another-one
  - data.json

which looks like this

{
  "an-entry-name": {
    "path": "an-entry-name",
    "title": "An Entry Name",
    "tags": ["whatever", "yeah"],
    "text": "This was contained in the markdown. Title and tags where in the json. Path was added automatically."
  },
  "another-one": {
    "path": "another-one" ,
    "title": "Another One",
    "date": "4/20/17",
    "text": "You can add arbitrary date to the json."
  }
}

i’m using this to create a psuedo-api of content which is hosted on github pages. i then made a seperate stateful app which loads the data.json and can pull in any assets based off the directory name.

the idea is to separate the site and the content. with a simple enough taxonomy i can re-use this structure across versions of my personal site. pretty highly specific, but, yeah.

usage

spod add [dirname]

  • add/update entry to the log data

spod remove [dirname]

  • remove from the log data

spod watch

  • watch added entries for changes and write to the log.
  • spins up a local server at port 3000 to access /data.json

todo

  • testing
  • clean up entry methods
  • use args for watch to use server, port, etc…
  • add arg for including markdown text or not in the json