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

@modwatch/core

v0.2.2

Published

TO BUILD ==

Downloads

5

Readme

TO BUILD

Dependencies

  1. NodeJS/NPM (Latest Stable Version)

Setup

  1. Open a terminal/command prompt
  2. cd to this directory
  3. npm install
  4. npm start

GENERAL

This site is a barebones MEAN stack web server without the M(ongo). It gets data from a decoupled API server. The build system is uses NPM scripts to run browserify, which keeps it as simple as possible for building on the server.

The frontend framework being used is Angular 1.4.x. Currently the goal for the Angular code is to move to the John Papa styleguide. This will allow for much more modular code, and a cleaner path to Angular 2.

Bootstrap 3 is the CSS library I use. I may move to Bootstrap 4 when it's stable, since I don't really worry about old browser support unless someone asks for it.

CONTRIBUTING

  1. Fork this repo
  2. Open an issue for the problem/enhancement you want to work on
  3. Create a branch that has to do with the issue you want to fix
  4. Implement your changes
  5. Make a pull request to this repo
  6. If there are no merge conflicts, and I've already approved the issue you created, I'll most likely merge your changes in

When making changes, do your best to follow the standards already set in other parts of the repo. Changes should not be noticeable when looking through source code. I would prefer all changes pass eslint with the .eslintrc in the root directory.

LINKS