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

run-project-commands

v1.0.0

Published

A powerful CLI toolkit for developers to run, manage, and automate project commands across JavaScript/TypeScript projects with task automation and workflow management

Readme

Run Project Commands (RPC)

npm version License: MIT Node.js Version

A powerful, developer-friendly CLI toolkit for running and managing project commands in JavaScript/TypeScript projects. Streamline your development workflow with automated task management, command execution, and project configuration.

✨ Features

  • Simple Command Execution: Run project commands with ease using the intuitive CLI interface
  • Project Information: Display package details directly from your terminal
  • System Diagnostics: Built-in doctor command to verify installation and compatibility
  • Developer-Friendly: Designed for JavaScript/TypeScript developers to increase productivity
  • Cross-Platform: Works on Windows, macOS, and Linux environments

🚀 Installation

Global Installation (Recommended)

We recommend installing run-project-commands globally to make the rpc command available in any terminal or directory on your system:

npm install -g run-project-commands

After global installation, you can run the rpc command from any terminal:

rpc

Alternative: Run with npx

If you prefer not to install globally, you can run it directly with npx:

npx run-project-commands
# or shorter:
npx rpc

📋 Usage

Basic Command

When you run rpc in a project directory, it will display the package name and version from the package.json file.

rpc

Available Commands

Doctor Command (rpc doctor)

The doctor command checks if your installation is healthy and working correctly:

rpc doctor

This command performs:

  • ✅ Verification of global RPC installation
  • 🔄 Checks for available updates
  • 🔍 Node.js compatibility validation
  • 💡 Troubleshooting recommendations

Command Options

# Display version information
rpc -v
rpc --version

# Display help menu and available commands
rpc --help

💻 Development

Want to contribute or build locally? Follow these steps:

  1. Clone the repository:

    git clone https://github.com/AdarshHatkar/run-project-commands.git
    cd run-project-commands
  2. Install dependencies:

    npm install
  3. Build the project:

    npm run build
  4. For development with auto-rebuild:

    npm run dev
  5. Link locally for testing:

    npm run link

🔍 Troubleshooting

Command not found after global installation

If you've installed the package globally but still get a "command not found" error when running rpc, try the following:

  1. Check your PATH environment variable:

    # On Windows (PowerShell)
    $env:PATH
       
    # On macOS/Linux
    echo $PATH
  2. Find the location of your global npm bin directory:

    npm config get prefix

    The global bin directory is typically <npm prefix>/bin on macOS/Linux or <npm prefix> on Windows.

  3. If needed, add the global npm bin directory to your PATH in your shell profile.

📊 Compatibility

  • Node.js: >=16.0.0
  • Platforms: Windows, macOS, Linux

� Future Plans

While we're planning to expand this tool to support various project types in the future, our current focus is on Node.js/JavaScript/TypeScript projects. We aim to make RPC a universal tool for developers across different technologies.

If you're interested in adding new functionality or extending support for other project types, feel free to raise a pull request! Contributions are always welcome.

�📄 License

MIT © Adarsh Hatkar

🔗 Links