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

hey-tushar

v1.0.5

Published

Tushar Singh's terminal portfolio - run with npx hey-tushar

Readme

tushar-dev

A one-shot terminal portfolio, distributed as an npm package.

npx tushar-dev

prints Tushar Singh's portfolio card straight to the terminal and exits. No menu, no prompts, no dependencies — just the message.

Editing it

Everything shown is one console.log template string inside index.js. Open index.js, edit the text between the backticks, save. What's inside those backticks is exactly what gets printed — nothing more, nothing less.

To add a line: add it inside the backtick string, in the position you want. To delete a line: delete it from inside the backtick string. There is no separate config object in this version — the text itself is the whole file.

Testing locally

node index.js

Or test the real global command the way an end user will run it:

npm link
tushar-dev

Then clean up:

npm unlink -g tushar-dev

Publishing

The npm website is only for your account and browsing packages — the publish step itself has to run from a terminal, since it needs to read and upload your local files:

npm login
npm publish

Check tushar-dev isn't already taken on npmjs.com first. If it is, change name in package.json and the bin key to match, then publish. From then on, anyone can run:

npx tushar-dev

Updating a published version

npm version patch   # 1.0.0 -> 1.0.1
npm publish

Publishing checklist

[ ] Edit the text inside index.js
[ ] Test with node index.js
[ ] Test with npm link + tushar-dev
[ ] Confirm "tushar-dev" is available on npmjs.com
[ ] npm login
[ ] npm publish
[ ] npm unlink -g tushar-dev (clean up local link)
[ ] Test from a different directory: npx tushar-dev