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

matembo-dev

v1.1.25

Published

A CLI tool for scaffolding full-stack projects with **Next.js** (frontend) and **Express.js** (backend) — ready to go in seconds.

Downloads

489

Readme

matembo-dev

A CLI tool for scaffolding full-stack projects with Next.js (frontend) and Express.js (backend) — ready to go in seconds.


Installation

You can use matembo-dev directly without installing it globally via npx:

npx matembo-dev <command>

Or install it globally to use it anytime:

npm install -g matembo-dev

Commands

create <AppName> — Scaffold a new fullstack project

Creates a new project folder with a Next.js frontend and an Express.js backend already set up inside it.

npx matembo-dev create MyApp

What gets created:

MyApp/
├── frontend/       ← Next.js starter
└── backend/        ← Express.js starter

After running the command, follow these steps:

# Start the frontend
cd MyApp/frontend
npm install
npm run dev

# Start the backend (in a separate terminal)
cd MyApp/backend
npm install
npm run dev

init <type> — Initialize a template in your current folder

Copies a starter template directly into your current working directory. Useful when you already have a project folder and just want to drop in a template.

Available types:

| Type | Description | | ----------- | -------------------------- | | backend | Express.js backend starter | | frontend | Next.js frontend starter | | fullstack | Both frontend and backend |

# Initialize a backend project in the current folder
npx matembo-dev init backend

# Initialize a frontend project in the current folder
npx matembo-dev init frontend

# Initialize a fullstack project in the current folder
npx matembo-dev init fullstack

After running init, follow these steps:

npm install
npm run dev

--start — Start the application

Starts your application using the configuration found in your project.

npx matembo-dev --start

Requires a tool.config.js or tool.config.json file in your project root.


--build — Build the application

Builds your application.

npx matembo-dev --build

⚙️ Configuration

matembo-dev looks for a config file in your project root. You can use any of these formats:

tool.config.json

{
  "port": 3000
}

tool.config.js

export default {
  port: 3000,
};

Or add it inside your package.json:

{
  "tool": {
    "port": 3000
  }
}

🗂️ Project Structure (after create)

MyApp/
├── frontend/
│   ├── app/
│   │   ├── (auth)/
│   │   │   ├── signin/
│   │   │   └── signup/
│   │   ├── context/
│   │   ├── services/
│   │   ├── globals.css
│   │   ├── layout.tsx
│   │   └── page.tsx
│   ├── components/
│   ├── icons/
│   ├── public/
│   ├── next.config.ts
│   ├── package.json
│   └── tsconfig.json
│
└── backend/
    ├── src/
    │   ├── config/
    │   ├── controllers/
    │   ├── middleware/
    │   ├── models/
    │   ├── routes/
    │   ├── utils/
    │   └── validators/
    ├── server.js
    ├── app.js
    └── package.json

create vs init — What's the difference?

| | create <AppName> | init <type> | | ---------------------------- | ------------------ | -------------------------- | | Creates a new folder | ✅ Yes | ❌ No | | Works in current folder | ❌ No | ✅ Yes | | Scaffolds frontend + backend | ✅ Always | ✅ Choose type | | Best for | Starting fresh | Adding to existing project |


🛠️ Requirements

  • Node.js v18 or higher
  • npm v7 or higher

📄 License

MIT © MatemboDev


🤝 Contributing

Have ideas or found a bug? Feel free to open an issue or pull request on the GitHub repository.


Built with ❤️ by MatemboDev