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

tplan

v1.0.3

Published

TODO

Readme

tPlan

A simple CLI tool for generating test plan documents.

Usage: tplan [options] [command]

Options:
  -h, --help               display help for command

Commands:
  init                     Setup directory and Git repo for adding test plans
  new <ticket>             Create new tPlan for a ticket
  latest                   Open the latest ticket (if exists)
  reset                    reset the default directory for test plans
  setdefault <setDefault>  set the default directory for tPlan
  seteditor <setEdit>      set the default text editor for tPlan -  options 'atom' 'code' 'subl'
  help [command]           display help for command

TODO

  • init - done!

    • Set up the working directory for new test plans to go in
    • Init a git repo in the chosen directory
  • new - Done!

    • Create a new markdown file to write a test plan in
    • Give config options for Ticket number, type of test, etc
    • Creates the doc with the parameters, ticket in the filename
    • adds date to file
    • Set 'latest' ticket, to allow easy retrieval of files
  • latest - Done!

    • Open the latest ticket, that was set in the 'new' step
  • Reset - Done!

    • Resets the default folder, and current ticket
  • SetDefault - Done!

    • Set default folder
  • SetCurrentTicket

    • Set current ticket
  • Set default text editor

    • Sets the editor from vscode, atom, subl or vim
  • list

    • List all current test plans
    • Is it really needed?
  • Delete?

    • Maybe not needed but handle deletion of files
  • Search

    • Make it easy to find a ticket's writeup
    • Maybe make it tplan open ...
  • Review

    • On created writeups, in the pass/fail section, could run through criteria and mark with a pass/fail on each one with a p and f