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

interactive-scripts

v0.1.1

Published

Interactive script runner for npm

Downloads

5

Readme

interactive-scripts

List all of your npm scripts from package.json and run one of your choosing in just one short command :)

Installation

Just add this to your global npm packages like so: npm install --global interactive-scripts or yarn global add interactive-scripts.

Usage

After installing globally with npm or yarn, simply run scripts in your terminal.

See the example gif where I demonstrate its use in an actual project:

demo gif

Why not just npm run or yarn run?

Good question.

yarn run already prints out the project's commands and opens a prompt for you to type the name of the command to run.

npm run also lists out the project's commands, but does not open a prompt.

So, the main differences between using your existing package manager's run and scripts is that scripts...

  • provides a scrolling interface of all of your scripts instead of listing them all out at once
  • allows you to select the command to run via arrow keys and enter instead of typing the name
  • is a whopping 1 character shorter than yarn run 🤷