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

witch-doctor

v0.0.3

Published

a command-line tool for pulling documentation from multiple git repositories into one project for static site generation.

Readme

Witch Doctor

witch doctor

a command-line tool for pulling documentation from several GitHub repositories into one project for static site generation.

Philosophy

Documentation thrives when two rules are followed:

  1. Authoring documentation occurs closest to the code it represents (hopefully in the same repo).
  2. Reading documentation occurs in one common place where it can enforce a habit.

Getting Started

First you will need to create a witch-doctor.json file in the directory you wish to merge documentation into. This file will look like:

{
    "projects": [
        {
            "name" : "<name>",
            "source": "<source directory>",
            "target": "<target directory>",
            "repository" : "<github repository name>",
            "branch" : "<repository name>",
            "token" : "<OAuth token> (optional for private repos)"
        }
    ]
}

Next install the witch-doctor npm package.

> npm install witch-doctor
> npm install -g witch-doctor

Finally, as part of a build, run witch-doctor.

> witch-doctor witch-doctor.json

What Happens?

Witch Doctor will clone all the repositories in your witch-doctor.json file and begin to copy the files from source to target. Once, all projects are processed, you can run the build script for your static site generator of choice: Jekyll, Hugo, etc.

Credit