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

see_it_done

v1.4.66

Published

Agile project template

Readme

see_it_done (from startup to the end)

Releases: npm Build Status codecov downloads license

Quality: CodeFactor DeepScan grade Known Vulnerabilities dependencies Status

Development: open issues closed issues last commit Maintenance commit activity

Github: code size repo size Github releases HitCount

Build History

Build History

Main npm keywords:

  • "front-end",
  • "back-end",
  • "cli",
  • "documentation",
  • "css",
  • "testing",
  • "iot",
  • "coverage",
  • "mobile",
  • "framework"
  • "robotics",
  • "math"

Framework keywords:

  • "lamed",
  • "console",
  • "cli",
  • "command-line"

Project Setup

AS A

  • Project owner
  • Project manager
  • Developer

I WANT TO

  • kick-start new projects and get the CI (the automatic build, unit testing, code coverage and NPM release pipline) up and running
  • auto upgrade dependencies
  • implement and debug unit tests easily and effectively

SO THAT I CAN

  • Finish fast and at the highest quality
  • Spend more time focus on new features
  • Easily refactor projects and dependencies

In short: From lift-off to touchdown - get to the goal as safely and as quick as possible.

After executing the following instructions, replace with your README text:

  • Copy contents of "see_it_start" to your project folder
  • Edit "package.json" and ".travis.yml" and replace "see_it_start" with your project name.
  • Execute following commands to setup the README.md
ll badges readme
ll readme usage
  • In the src folder of see_it_done project edit
    • Add your project to 'package_zetup.json' and
    • execute 'node src/packageSync'

To customize more:

  • In the src folder of see_it_done project edit
    • 'package_add.json' (add default items for all your projects package files)
    • 'package_update.json' (add items you want to sync across all your projects package files)
    • 'package_zetup.json'
      • add the projects who's package files you want to sync to
      • add the project package files you want to exclude when defaults are synced
      • add the npm commands you want to automatic run across projects
      • set the default timeout time
      • set you .gitIgnore file you want to sync accross all your projects
  • When all is setup, run the following command to sync all package.json files across your projects:
node src/packageSync
  • When all is setup, run the following command to create batch scripts across your projects:
node src/npmBatch

There are already batch scripts defined to do the following:

  • Commit accross all projects:
    • local, (local commit only)
    • fast, (commit and push)
    • safe (commit and push if all tests completed successfully)
  • Pull accross all projects
  • Remove files from git for all projects (after update of .gitIgnore)
  • Upgrade all dependencies across all projects (and run CI pipeline)
  • Run unit tests across all projects

Helpful tools

About Team

license