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

@guren/plugin-cloudflare

v0.2.1

Published

Deploy a [Guren](https://guren.dev/) application to Cloudflare Workers, with D1 as the database.

Downloads

271

Readme

@guren/plugin-cloudflare

Deploy a Guren application to Cloudflare Workers, with D1 as the database.

bunx guren plugin @guren/plugin-cloudflare
bun add @guren/plugin-cloudflare

Installing registers a cloudflare:build command and scaffolds wrangler.jsonc on the first build.

Build and deploy

bunx guren cloudflare:build
bunx wrangler deploy

cloudflare:build runs your app's build script, then assembles a .cloudflare/ directory containing the worker entry, static assets for Workers Static Assets, and flattened D1 migrations. It is generated output — add it to .gitignore and rebuild before every deploy.

API

  • createWorkersHandler(app) — wraps a Guren Application in a Workers module handler. Boot is lazy and deduplicated on the first request, because bindings only arrive with fetch and cannot be read at module scope.

  • getWorkersEnv<Env>() — exposes the first request's bindings to boot-time config through a write-once holder. Use it to hand a D1 binding to the ORM:

    import { createD1Database } from '@guren/core'
    import { getWorkersEnv } from '@guren/plugin-cloudflare'
    
    const database = createD1Database({
      binding: () => getWorkersEnv<{ DB: unknown }>().DB,
    })

    The binding is a resolver, not a value — it must be read lazily.

  • cloudflarePlugin() — the service provider factory, registered automatically by guren plugin.

Things Workers changes

Workers has no filesystem and shares no memory between requests, so a few defaults do not apply:

  • Sessions and OAuth state must be database-backed. Each request may land on a different isolate. The in-memory defaults work locally and then drop every session in production. Use DatabaseSessionStore and DatabaseOAuthStateStore.
  • Migrations are applied out of band. wrangler d1 migrations apply owns the lifecycle; the app never migrates itself.
  • APP_KEY is required. Sessions and CSRF are signed with it, and the worker throws at startup without it.

See the Cloudflare Workers deployment guide for the full path from an empty account to a deployed app, including D1 setup, secrets, free-plan limits, and local development.

License

MIT