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 🙏

© 2024 – Pkg Stats / Ryan Hefner

term-stats

v0.0.7

Published

check npm download stats in your terminal :computer: :100:

Downloads

10

Readme

term-stats

Check npm download stats in your terminal. 💯 💻

npm license

term-stats demo

💎 😍

Installation

Well, here we go again.

Let the awesomeness breathe. (duh!)

$ yarn global add term-stats

In case you like npm more,

$ npm i -g term-stats

Usage

Step 1. Add some pretty(🙈) config.

A config file is what helps the package display stats for only the ones you care about. In this step you are gonna create one, and put it where it belongs.

  • Add Environment variable – TERM_STATS_CONFIG

Adding an environment variable is a different procedure in every OS. If you are on windows, you can hit the window key and type Environment variables (Or you could Google). On linux/unix,

  • if you're using zsh, that's probably in your home directory's ~/.zshrc file
  • if you're using bash, that could be your bash_profile file or ~/.bashrc file
  • if you're using fish, use set -gx key value in your ~/.config/fish/config.fish file

Open the required file, and enter the following line:

export TERM_STATS_CONFIG = '/usr/lib'

Change the contents inside the quotes to wherever you want to save the file. To check if it was successful, fire a new terminal and run this,

$ echo $TERM_STATS_CONFIG
'/usr/lib/' #Directory location of your config file. (See step 2.)

🎉

Step 2. Make a file named term-stats.json in the directory you chose above.

$ cd /usr/lib/
$ touch term-stats.json && nano term-stats.json

Feel free to open it in whatever editor you hang out with.

See the example term-stats.json to see how it works. You need to have a key named packages, which is an array of the names of packages you want the stats for.

{
    "packages":["express", "npm", "yarn", "bower", "react", "react-native"]
}

Save it and move on. You are done. The next step is gonna be brilliant.

Party Step All you have to do now is fire a terminal, and type in

$ term-stats

And the party begins.

🎉 😂