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

st-run

v2.0.0-beta.4

Published

A chainable, faster, always up-to-date npx and system command executor

Downloads

48

Readme

npx replacement: st-run st-rm-rf dist ++ system:tsc

💨Just like npx but chainable, way faster and always using @latest of any command 💨

🎉 Get rid of node scripts to chain commands 🎉

🚀Get rid of direct & out-dated CLI dependencies 🚀

🧑‍🤝‍🧑 Cross-platform and end-2-end tested ✨

Performance

~2x faster than npx when your machine is online:

~5x faster than npx when your machine is offline:

And it always checks for the @latest version when your machine is online.

Usage

You can use st-run in npm scripts like this:

{
    "name": "your-node-module",
    "scripts": {
        "copy-smth": "st-run st-cp package.json package.json2"
    },
    "dependencies": {
        "st-run": "latest"
    }
}

This way you may get rid of some direct dependencies and make sure the CLI tools being used by end-users are always up to date.

Or install it globally like npx:

npm i -g st-run

And use it globally just like npx:

st-run st-cp package.json package.json2

commandA arg1 ++ commandB arg1 arg2 Chaining Syntax

You can get rid of special node scripts to chain commands by letting st-run chain them for you:

st-run st-cp package.json package.json2 ++ st-cp package.json2 package.json3

As you can see, a simple + chains two or more commands. There is no command count limit.

command@specificVersion Syntax

With st-run you can have multiple cached versions at the same time (just like with maven, gradle etc.):

st-run [email protected] package.json package.json2 ++ [email protected] package.json2 package.json3

Cool?

system:command Syntax

Oh, you want to run a command that is not an npm script? st-run got you covered:

st-run system:rm -rf dist + system:tsc

This also works for globally installed npm packages that you don't want to update on-the-fly.