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 🙏

© 2025 – Pkg Stats / Ryan Hefner

localdocs

v0.3.1

Published

This is tool to provide embedded docs into a repo. The idea is to reduce context switching and allowing tighter coupling between docs and code.

Downloads

328

Readme

Repo Docs

This is tool to provide embedded docs into a repo. The idea is to reduce context switching and allowing tighter coupling between docs and code.

This tool mostly provides auto generated navigation through your documentation, A navigation tree will always be created and you can specify categories to improve navigation.

Generating docs

Running the script is done by calling localdocs. This will look for any markdown files within the project directory with the documentation extension which defaults to doc.md.

This will generate a docs.doc.md file at the root of the repository.

Options

You can pass an entry point as the second argument to only search for documentation files within a specified directory:

npm run localdocs ./test

| flag | description | value | | -------------- | ------------------------------------------------ | ----------------- | | e | file extension to use | (default) .doc.md | | x | comma seperated list of blobs or regex to ignore | (default) '' | | include-node | should include files in node_modules | (default) flase | | h | show help | |

It is advisable to add generating the docs to your pre-commit git hook.

The command will modify and generate the documentation files when it runs so you can add something like the below example:

npm run generate:docs
git add *.doc.md

Categories

Creating a category is done by adding a category tag to any documentation page e.g.

<#my category>

When the documentation pages are walked these categories will be found and links created on your documentation homepage in the Categories section.