Application example Bindings

Use Browser Rendering in a real application path

Browser Rendering lets Workers drive a headless browser for screenshots, PDFs, and page automation.

This example shows the real browser path people actually need: one binding, one title-read route, and one smoke check through the dev server.

It is intentionally smaller than a full PDF pipeline, but it uses the same Devflare idea: a narrow worker route on top of a bridge-backed local browser lane.

Config focus: Single browser binding
Runtime shape: Launch puppeteer with the Worker binding and close it cleanly
Best use: Small screenshot, title-read, or PDF-generation entrypoints

Start by wiring the binding clearly in config

Minimal browser config

import { defineConfig } from 'devflare/config'

export default defineConfig({

name: 'browser-example',

files: {

fetch: 'src/fetch.ts'

bindings: {

browser: {

BROWSER: 'browser-resource'

}

})

Build the application flow around the binding

Treat this as the app-level Browser Rendering path: the route, event handler, or service module receives a real request and uses the binding to do useful work.

Keep product limits, remote ownership, and fallback behavior visible in the code around the binding instead of hiding everything behind a vague utility too early.

Keep the first route tiny so launch, navigation, and cleanup are the only moving parts you have to trust.
If the real feature is PDF generation, this same pattern is the foundation for that worker path.

Read one page title with Puppeteer

import puppeteer from '@cloudflare/puppeteer'

import { env } from 'devflare/runtime'

export async function fetch(): Promise<Response> {

const browser = await puppeteer.launch(env.BROWSER as Parameters<typeof puppeteer.launch>[0])

try {

const page = await browser.newPage()

await page.goto('https://example.com/', { waitUntil: 'load' })

return Response.json({ title: await page.title() })

} finally {

await browser.close()

}

Keep production boundaries visible

Config focus: Single browser binding.
Runtime shape: Launch puppeteer with the Worker binding and close it cleanly.
Best use: Small screenshot, title-read, or PDF-generation entrypoints.

The Devflare value is the bridge-backed local lane

Browser work is still heavier than most bindings, but Devflare gives it a real local/dev story instead of forcing you to document only the production path. Keep the first route narrow enough that launch failures are easy to diagnose.

Testing Browser Rendering

Browser tests should usually be integration-flavored: either drive the worker in dev or exercise a thin smoke path that proves the binding can launch and fetch.

Analytics Engine

Analytics Engine is modeled cleanly in Devflare config and generated types, but the repo evidence points to a lighter local story than KV, D1, and R2.