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

@stewie-js/adapter-cloudflare

v0.9.0

Published

Cloudflare Workers adapter for the Stewie framework

Readme

@stewie-js/adapter-cloudflare

Work in progress.

Stewie is under active development and not yet stable. APIs may change between releases. Not recommended for production use yet.

Cloudflare Workers adapter for Stewie. Workers natively speaks the Web Request / Response API, so this adapter is a thin wrapper that connects your Stewie app handler to the Module Worker fetch entry.

Part of the Stewie framework.

Install

pnpm add @stewie-js/adapter-cloudflare

The example below also uses @stewie-js/server and @stewie-js/core, which are a common pairing but not required by the adapter itself — it works with any handler that accepts a Request and returns a Response.

Usage

// worker.ts
import { createCloudflareHandler } from '@stewie-js/adapter-cloudflare'
import { renderToString } from '@stewie-js/server'
import { jsx } from '@stewie-js/core'
import App from './App.js'
import template from './index.html'

export default createCloudflareHandler(async (req) => {
  const { html, stateScript } = await renderToString(jsx(App, {}))
  const page = template
    .replace('<!--ssr-outlet-->', html)
    .replace('</body>', `  ${stateScript}\n</body>`)
  return new Response(page, {
    headers: { 'content-type': 'text/html; charset=utf-8' },
  })
})

wrangler.toml:

name = "my-stewie-app"
main = "worker.ts"
compatibility_date = "2026-01-01"

API

| Export | Description | |---|---| | createCloudflareHandler(app) | Returns a Module Worker default export object with a fetch method, ready to export default from your worker entry | | StewieApp | Type: (request: Request) => Response \| Promise<Response> | | CloudflareWorker | Type: the Module Worker shape returned by createCloudflareHandler | | CloudflareExecutionContext | Minimal local type for Cloudflare's ExecutionContext (no peer dependency on @cloudflare/workers-types) |

Unhandled errors thrown by the app handler are caught, logged to console.error, and converted to a 500 response automatically.

Accessing env and ctx

env (bindings: KV, R2, D1, secrets, env vars) and ctx (with waitUntil and passThroughOnException) are accepted by the returned fetch to satisfy the Module Worker contract, but are not yet plumbed through to the Stewie app handler. This is a v1 limitation — a broader context-propagation design is needed first so the access pattern is consistent across runtimes.

If you need env or ctx today, wrap the returned handler:

const handler = createCloudflareHandler(app)

export default {
  async fetch(req: Request, env: Env, ctx: ExecutionContext) {
    // do something with env or ctx here, e.g. ctx.waitUntil(logAccess(req))
    return handler.fetch(req, env, ctx)
  }
}