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

@timbenniks/turbo-project

v0.1.1

Published

A whimsical CLI that scaffolds your full-stack project in one command

Downloads

172

Readme

@timbenniks/turbo-project

Go from zero to a fully deployed full-stack app in one command.

turbo-project is an interactive CLI that scaffolds a complete project, provisions infrastructure, and leaves you ready to npm run dev — no manual wiring required.

Quick Start

npx @timbenniks/turbo-project

The wizard collects the full plan first, checks only the tools needed for the steps you selected, then executes the setup.

You can also skip prompts with flags:

npx @timbenniks/turbo-project --name my-app

What You Get

Depending on what you select, turbo-project can set up:

  • Next.js 16 with TypeScript and Tailwind CSS v4
  • shadcn/ui components using the stable default scaffold, with optional custom preset support
  • Drizzle ORM with a starter schema and config
  • Neon serverless Postgres database, provisioned and connected
  • Vercel project linked to your repo with automatic deployments
  • GitHub repository (optional, public or private)
  • Environment variables synced to .env.local
  • AGENTS.md so LLM coding assistants understand your project out of the box
my-app/
├── app/                # Next.js App Router
├── components/         # shadcn/ui components
├── db/
│   └── schema.ts       # Drizzle schema (starter file)
├── drizzle.config.ts   # Drizzle config (reads DATABASE_URL)
├── .env.local          # Neon connection strings (auto-generated)
├── AGENTS.md           # LLM-friendly project documentation
├── README.md           # Project readme
└── ...                 # Standard Next.js files

Every step is optional. You can scaffold a fresh project, or skip scaffolding and run selected setup steps against an existing directory with the same name.

How It Works

  1. Wizard — Collects project name and optional setup steps
  2. Conditional preflight — Checks only the CLIs required by selected steps
  3. Scaffold — Optionally runs shadcn init with defaults or a custom preset
  4. Drizzle — Optionally installs Drizzle and writes starter database files
  5. Git + GitHub — Optionally initializes git, creates a remote, and pushes
  6. Vercel + Neon — Optionally links Vercel, provisions Neon, and pulls env vars
  7. Documentation — Optionally generates AGENTS.md and README.md

If a selected step fails after creating a new project, the CLI removes the local project directory so you do not end up with a half-finished local scaffold. If you chose to run against an existing directory, it will not delete that directory.

Prerequisites

| Tool | Required | Install | |------|----------|---------| | Node.js v18+ | Yes | nodejs.org | | Git | Only for Git/GitHub/final commit | git-scm.com | | Vercel CLI | Only for Vercel/Neon/env vars | npm i -g vercel | | GitHub CLI | Only for GitHub repo creation | cli.github.com |

The CLI reports missing tools after you confirm the plan, so skipped steps do not require their tools to be installed.

Customizing shadcn/ui

By default, turbo-project uses shadcn/ui's built-in defaults. If you already have a working preset ID, pass it with --preset:

npx @timbenniks/turbo-project --name my-app --preset yourPresetId

If the custom preset cannot be applied, the CLI retries with shadcn defaults so project creation can continue.

Tech Stack

| Layer | Technology | |-------|-----------| | Framework | Next.js 16 | | Language | TypeScript | | Styling | Tailwind CSS v4 | | Components | shadcn/ui | | ORM | Drizzle | | Database | Neon (serverless Postgres) | | Hosting | Vercel |

Contributing

git clone https://github.com/timbenniks/Turbo-Project.git
cd Turbo-Project
npm install
npm run build
npx .

License

MIT