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

@pubflow/native

v1.0.6

Published

Minutes from idea to a page + API. Hono + TanStack Router + Vite. Same fetch on Node, Bun, Docker, or Cloudflare Workers.

Readme

@pubflow/native

Intermediate stack on Hono, TanStack Router, and Vite. Minutes from idea to a page + /api. The same fetch runs on Node, Bun, Docker, or Cloudflare Workers — Workers is optional. Pages cannot import getDb(). Any TypeScript app can use it; Pubflow auth is optional.

bun add @pubflow/native @tanstack/react-router hono react react-dom
bun add -d vite
import { defineConfig } from 'vite'
import native from '@pubflow/native/vite'

export default defineConfig({
  plugins: [native()],
})

New app — clone only starter/:

npx degit pubflow/native/starter my-app
cd my-app && bun install && bun run dev

Layout

app/pages/      React routes — [id].tsx receives { id }
app/api/        Hono → /api/...  (.get / .post)
app/lib/        domain code (not mounted)
app/actions/    functions → POST /api/actions/<id>

The client build fails if a page imports getDb(). Put secrets in app/api or app/actions. Optional: usePathParams() from this package.

Pubflow Actions are same-origin POST JSON, not RSC and not gRPC. The UI path is HTTP on this process; gRPC can live behind Native later if another service talks to it.

Optional server auth: import { requireAuth, requireRole } from '@pubflow/native/auth' (Flowless). Not pulled into the client. Login UI stays @pubflow/react.

Optional: @pubflow/native/db (Kysely; Hyperdrive on Workers for Postgres/MySQL), ./cache, ./mail, ./rate-limit, ./http (getClientIp, corsFromEnv). Peers are optional.

Docs: github.com/pubflow/native — pages, backend, env, upgrade.