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

tiniest-dev-agent

v1.0.0

Published

A lightweight local agent that maps project aliases to filesystem paths and opens them in your chosen IDE

Readme

🧭 dev — Personal IDE Launcher

A lightweight CLI tool to open your projects by alias, instantly, in your favorite IDE.
Type dev gw-client and jump straight into your workspace — no hunting through folders.


🔧 Installation

Option 1: Install via npm (Recommended)

npm install -g dev-agent

Or use with npx without installing:

npx dev-agent <alias>

Option 2: Manual Installation

Create a personal bin folder and place the script there:

mkdir -p ~/bin
curl -o ~/bin/dev https://raw.githubusercontent.com/diegoferreyra/dev-command/main/dev
chmod +x ~/bin/dev

Make sure your shell can find it:

echo 'export PATH="$HOME/bin:$PATH"' >> ~/.zshrc
source ~/.zshrc

You can also symlink to /usr/local/bin/dev or /opt/homebrew/bin/dev if you prefer.


3. Create your configuration file

Create a file called ~/.dev-locations.json:

nano ~/.dev-locations.json

Example:

{
  "ide": "app:Cursor",
  "aliases": {
    "gw-lms":    { "folder": "~/WebDevelopment/greenwave/greenwave-lms" },
    "gw-client": { "folder": "~/WebDevelopment/greenwave/greenwave-client" },
    "gw-commhub":{ "folder": "~/WebDevelopment/greenwave/greenwave-comm-hub" },
    "gw-api":    { "folder": "~/WebDevelopment/greenwave/greenwave-api" },
    "gw-search": { "folder": "~/WebDevelopment/greenwave/greenwave-search-api" }
  }
}

4. (Optional) Custom config path

If you want to keep your config somewhere else, export a DEV_CONFIG variable:

export DEV_CONFIG="$HOME/dev-locations.json"

Add it permanently to your shell config if you like:

echo 'export DEV_CONFIG="$HOME/dev-locations.json"' >> ~/.zshrc

🚀 Usage

| Command | Description | |----------|-------------| | dev <alias> | Opens the alias folder in your configured IDE | | dev <a1> <a2> ... | Opens multiple aliases (each in a new window) | | dev --list | Lists all known aliases | | dev --config | Prints the active config file path |

Example session:

dev gw-client
dev gw-client gw-api gw-search
dev --list

Each alias opens in a separate window of your IDE.


🧠 IDE Options

The "ide" key in your config defines how projects open:

| Value | Behavior | |--------|-----------| | "cursor" | Uses the Cursor CLI (cursor -n <folder>) | | "code" | Uses the VS Code CLI (code -n <folder>) | | "app:Cursor" | Opens the macOS app Cursor | | "/absolute/path/to/binary" | Uses a direct path to your IDE binary |


💡 Tips

  • Make sure your IDE's CLI command is available in your PATH.
  • Supports multiple aliases per run.
  • Works with Cursor, VS Code, and any macOS app name.
  • Uses open -n -a <AppName> as fallback.

License

MIT