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

render-create

v0.2.0

Published

CLI to scaffold and deploy applications on Render with best practices, Cursor rules, and Infrastructure as Code

Readme

render-create

CLI tool to scaffold Render projects with Cursor rules, linting configs, and templates. Supports both preset-based and composable project creation.

Quick Start

npx render-create my-app

That's it. You'll get an interactive prompt to choose your stack, and a fully configured project ready to deploy.

Features

  • One command setup - Go from zero to deployed in minutes
  • Infrastructure as Code - Auto-generated render.yaml Blueprint
  • AI-ready - Cursor rules for intelligent code assistance
  • Modern stacks - Next.js, Fastify, FastAPI, and more
  • Composable - Mix frontends, APIs, workers, and databases
  • Best practices - Linting, TypeScript, and sensible defaults

Usage

# Interactive mode (recommended)
npx render-create my-app

# Use a preset directly
npx render-create my-app --preset fastify-api

# Composable mode - pick your own stack
npx render-create my-app --composable

# Keep existing project rules in sync
npx render-create sync

# Check if rules are up to date (CI-friendly)
npx render-create check --ci

Available Presets

| Preset | Stack | Database | | ---------------- | ------------------------------ | ---------- | | next-fullstack | Next.js + Tailwind + Drizzle | PostgreSQL | | next-frontend | Next.js + Tailwind (static) | - | | vite-spa | Vite + React + Tailwind | - | | fastify-api | Fastify + Drizzle + Zod | PostgreSQL | | fastapi | FastAPI + SQLAlchemy | PostgreSQL | | multi-api | Fastify + FastAPI side-by-side | - |

Composable Mode

Build exactly what you need by mixing components:

npx render-create my-app --composable

Frontends

  • Next.js - React framework with App Router
  • Vite - Fast React SPA

APIs

  • Fastify - Node.js with Drizzle ORM
  • FastAPI - Python with SQLAlchemy

Workers

  • Background workers - TypeScript or Python
  • Cron jobs - Scheduled tasks
  • Workflows - Render Workflows with SDK

Infrastructure

  • PostgreSQL - Managed database
  • Redis - Managed cache

What You Get

Every project includes:

my-app/
├── src/                    # Your application code
├── .cursor/rules/          # AI coding assistance rules
├── render.yaml             # Infrastructure as Code
├── biome.json / ruff.toml  # Linting configuration
└── package.json            # Dependencies

Render Blueprint

The generated render.yaml defines your entire infrastructure:

services:
  - type: web
    name: my-app
    runtime: node
    buildCommand: npm install && npm run build
    startCommand: npm start
    healthCheckPath: /health
    envVars:
      - key: DATABASE_URL
        fromDatabase:
          name: my-app-db
          property: connectionString

databases:
  - name: my-app-db
    postgresMajorVersion: 16

Cursor Rules

AI-assisted development with framework-specific guidance:

| Rule | Description | | ---------------- | -------------------------------- | | general.mdc | Project conventions and patterns | | typescript.mdc | TypeScript best practices | | react.mdc | React and component patterns | | nextjs.mdc | Next.js App Router conventions | | fastify.mdc | Fastify API patterns | | drizzle.mdc | Drizzle ORM usage | | workflows.mdc | Render Workflows SDK |

Deploy to Render

After scaffolding, deploy in one click:

Deploy to Render

Or connect your repo to Render and it will automatically detect the render.yaml Blueprint.

Commands

render-create [name]

Create a new project. If no name is provided, you'll be prompted.

Options:

  • -p, --preset <name> - Use a preset (skip prompts)
  • -c, --composable - Enable composable mode
  • -y, --yes - Accept defaults

render-create sync

Update Cursor rules to the latest version.

Options:

  • -f, --force - Overwrite without prompting
  • --dry-run - Preview changes

render-create check

Verify rules are in sync.

Options:

  • --ci - Exit code 1 if out of sync

Contributing

We welcome contributions!

# Clone and setup
git clone https://github.com/R4ph-t/render-create-demo.git
cd render-create-demo
npm install

# Build and test
npm run build
npm test

# Test locally
npm link
render-create my-test-app

Releases

To create a new release:

npm run release:patch  # 1.0.0 → 1.0.1
npm run release:minor  # 1.0.0 → 1.1.0
npm run release:major  # 1.0.0 → 2.0.0

This will automatically:

  1. Run lint, build, and tests
  2. Bump the version in package.json
  3. Create a git commit and tag
  4. Push to GitHub

GitHub Actions will then create a release with auto-generated release notes.

License

MIT - see LICENSE for details.