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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@gaurav-udawant/pipecore

v1.0.3

Published

A powerful, interactive Command Line Interface (CLI) tool for rapidly scaffolding and managing scalable MERN stack microservices. Developed by [@gaurav-udawant](https://github.com/gaurav-udawant).

Readme

🚀 Pipecore CLI

A powerful, interactive Command Line Interface (CLI) tool for rapidly scaffolding and managing scalable MERN stack microservices. Developed by @gaurav-udawant.

@gaurav-udawant/pipecore automates the boring parts of setting up a microservices architecture. It generates production-ready Express servers, Mongoose models, Routers, and automatically configures your API Gateway and Environment variables.

✨ Features

  • Interactive CLI: Built with inquirer and beautifully formatted with chalk.
  • Instant Boilerplate: Generates standard MVC-style folders and files (.controller.ts, .service.ts, .model.ts, etc.).
  • Auto Gateway Configuration: Automatically appends proxy rules to your API Gateway.
  • Port Management: Dynamically assigns and tracks ports for new services to avoid conflicts.
  • TypeScript Ready: Fully configured with tsconfig.json and type definitions.

📦 Installation

Install the Pipecore CLI globally on your machine so you can use it across any of your microservice projects:

npm install -g @gaurav-udawant/pipecore

🛠️ Getting Started & Usage
⚠️ IMPORTANT PROJECT STRUCTURE RULE: To ensure the API Gateway configuration and dynamic Port tracking work perfectly, you MUST run this CLI inside a services directory.

Step-by-Step Guide:

1. Create your root project and services directory:
    Open your terminal and create a main project folder, then create a services folder inside it.
    mkdir my-microservices-app
    cd my-microservices-app
    mkdir services
    cd services

2. Setup your Gateway (Prerequisite):
Ensure you have your gateway folder initialized inside the services directory before generating new microservices, as Pipecore will attempt to auto-wire the new routes into it.

3. Run the Pipecore CLI:
Make sure your terminal is currently inside the services folder, then run:
    pipecore

4. Follow the Interactive Prompts:
The CLI will ask for the name of your new service (e.g., auth, payment, user). It will then automatically:

Create the folder structure parallel to your gateway.

Generate all necessary boilerplate files.

Create a package.json and .env with an auto-assigned PORT.

Update your API Gateway routes.

Run npm install to fetch dependencies for the new service.

📂 Expected Folder Structure
After running the tool, your workspace will look exactly like this:
    my-microservices-app/
 └── services/
      ├── gateway/
      ├── auth/
      │    ├── src/
      │    │    ├── app.ts
      │    │    ├── auth.controller.ts
      │    │    ├── auth.model.ts
      │    │    ├── auth.router.ts
      │    │    └── ...other files
      │    ├── package.json
      │    ├── tsconfig.json
      │    └── .env              
      └── payment/               # ✨ Another generated service