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-kilat

v0.2.1

Published

Scaffold a new Kilat project — Cloudflare Workers + Hono + D1 + Inertia v3 boilerplate with template selection (React/Svelte/Vue, vanilla CSS/Tailwind).

Readme

create-kilat

Scaffold a new Kilat project — Cloudflare Workers + Hono + D1 + Inertia v3 boilerplate with auth, roles, SSR, migrations, and PBKDF2 password hashing. Edge-native, zero-ops.

Usage

bun create kilat@latest my-app

Or in the current directory:

bunx create-kilat@latest .

The interactive prompt uses arrow-key navigation (↑/↓ to select, Enter to confirm) — just like npm create vite:

  1. Select a JavaScript framework — React 19, Svelte 5, or Vue 3
  2. Select a styling approach — Vanilla CSS or Tailwind CSS v4

Templates

| Template | Stack | Branch | | ----------------- | ---------------------------------- | ------------------------- | | default | React 19 + vanilla CSS | main | | svelte-vanilla | Svelte 5 + scoped <style> CSS | template/svelte-vanilla | | vue-vanilla | Vue 3 + scoped <style> CSS | template/vue-vanilla | | react-tailwind | React 19 + Tailwind CSS v4 | template/react-tailwind | | svelte-tailwind | Svelte 5 + Tailwind CSS v4 | template/svelte-tailwind| | vue-tailwind | Vue 3 + Tailwind CSS v4 | template/vue-tailwind |

Select interactively or via --template:

bun create kilat@latest my-app --template svelte-vanilla

Options

| Flag | Description | | ---------------- | ------------------------------------------------ | | --help, -h | Show help | | --no-install | Skip running bun install | | --template <n> | Use template directly (skip both prompts) |

What it does

  1. Prompts for a project name (if not provided).
  2. Prompts for a framework (React, Svelte, Vue) — arrow-key selection.
  3. Prompts for styling (vanilla CSS, Tailwind) — arrow-key selection.
  4. Downloads the selected template branch from GitHub.
  5. Strips dev-only files (screenshots, .env, etc.).
  6. Patches wrangler.toml: renames the Worker and resets the D1 database_id so the user configures their own.
  7. Renames package.json to the project name.
  8. Runs bun install (unless --no-install).

Next steps after scaffold

cd my-app
bun run db:migrate    # create local D1 schema
bun run build         # build client assets + SSR bundle
bun dev               # start wrangler dev server (http://localhost:8787)

For production deployment, create a D1 database and update wrangler.toml:

wrangler d1 create my-app       # paste the database_id into wrangler.toml
wrangler d1 migrations apply my-app --remote
bun run build
wrangler deploy

License

MIT