Devflare Docs
Starter example Bindings

A small Browser Rendering example you can adapt quickly

This example shows the real browser shape most people care about: launch a browser, read one page title, close the browser cleanly.

It is intentionally smaller than a full PDF pipeline, but it uses the same worker-side idea: the browser binding is real infrastructure, not a pretend local object.

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

Then use it in one honest runtime path

  • 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

Keep the first version boring on purpose

The example is small, not cheap

Browser work is still heavier than most bindings. Keep your first path focused enough that failures are easy to diagnose.

Previous

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.

Next

Analytics Engine

Analytics Engine is modeled cleanly in Devflare config and generated types, but the repo evidence points to a lighter local story than the first-class storage bindings.