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

@hyrious/dev-cmd

v0.1.2

Published

a shell helper

Downloads

6

Readme

dev-cmd

dev is a command-line tool that modifies commands before run.

npm i -g @hyrious/dev-cmd
dev --add proxy ... -c http.proxy=socks5://localhost:1080
# proxy = ... -c http.proxy=socks5://localhost:1080
dev proxy git clone XXX
# actually run: git clone XXX -c http.proxy=socks5://localhost:1080
dev --remove proxy
# removed proxy

The simplest example above just replaces ... with original command line, where it was git clone XXX.

Now let's add something more useful than that!

--add {cmd} {rule} / -A

Add/replace {cmd} with rule after it. If no rule presents, it does nothing.

dev -A hello echo "hello world!"
dev hello
=> hello world!

! Note: Windows users will encounter errors bacause echo is not a program but a shell command.

--starts-with {prefix} / =

Works only when original command starts with {prefix}. For example,

dev -A proxy = git ... -c http.proxy=socks5://localhost:1080

means that, only dev proxy git XXX will be modified by this rule.

Different {prefix} won't affect other rules imported by the same {cmd}, which means you can do this:

dev -A proxy ... --http-proxy=http://localhost:1080
dev -A proxy = git ... -c http.proxy=socks5://localhost:1080
dev -A proxy = aria2c ... --all-proxy=http://localhost:1080
dev -A proxy = scoop scoop config proxy http://localhost:1080 && ...

--remove {cmd} [--all] / -R

Remove {cmd}. It won't affect rules with {prefix} having the same {cmd}. To remove them too, add --all.

--starts-with {prefix} / =

Just like -A, remove specific {cmd} and {prefix}.

dev -R proxy
dev -R proxy = git
dev -R proxy --all

--plugin {path/to/plugin.js} [--save] / -P

You can add more complex rules with plugins. Here is an example.

module.exports = dev =>
  dev.add('proxy', {
      // you can use regex here, but keep in mind it only
      // matches the first argument, which is the command itself,
      // like `git`, `scoop`
      startsWith: 'scoop',
      run(cmd) {
          dev.sh('scoop', ['config', 'proxy', 'http://localhost:1080'])
          dev.sh(cmd)
      },
      remove() {
          dev.sh('scoop', ['config', 'rm', 'proxy'])
      }
  })

If --save presents, it will write this plugin's path into .dev.json's plugins list, see below.

--list / -L

Show rules.

.dev.json

dev will automatically load .dev.json at current & home folder.

{ "rules": [
    { "name": "proxy",
      "startsWith": "git",
      "run": ["...", "-c", "http.proxy=socks5://localhost:1080"]
    }
  ],
  "plugins": [
    "~/plugin.js"
  ]
}