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

create-testdemo

v1.0.3

Published

Create a Node.js project from my industrial-standard template

Readme

create-testdemo

CLI tool jo aapke apne industrial-standard Node.js template se naya project banata hai — bilkul npm create vite jaisa.

📁 Package Structure

create-testdemo/
├── index.js          # CLI entry point (scaffolding logic)
├── package.json
├── README.md
└── template/          # Ye poora folder naye project me copy hota hai
    ├── package.json    # {{PROJECT_NAME}} placeholder, auto-patched
    ├── gitignore        # renamed to .gitignore at scaffold time
    ├── .env.example
    ├── README.md
    └── src/...

🧪 Local Testing (publish se pehle)

Publish kiye bina hi local test kar sakte ho:

cd create-testdemo
npm link
create-testdemo my-app

Ya seedha:

node index.js my-app

🚀 Publish to npm

npm login
npm publish

Publish hone ke baad koi bhi is tarah use kar sakta hai:

npm create testdemo my-app
# ya
npx create-testdemo my-app

⚙️ CLI kya karta hai

  1. template/ folder ko target directory me copy karta hai (fs.cpSync)
  2. gitignore file ko .gitignore me rename karta hai (npm publish .gitignore ko automatically strip kar deta hai, isliye template me use bina-dot naam se rakha gaya hai)
  3. package.json me {{PROJECT_NAME}} placeholder ko folder ke naam se replace karta hai
  4. .env.example se .env auto-create karta hai
  5. Poochta hai ki npm install abhi chalana hai ya nahi

➕ Template update karna ho to

Bas template/ folder ke andar apna naya standard code daal do — jo bhi isme hoga wahi har naye project me copy hoga. package.json me sirf name field {{PROJECT_NAME}} hi rehne dena, baaki sab as-is rakh sakte ho.