Starter example Bindings

A small R2 example you can adapt quickly

This example uses one private bucket and one route, which is still the cleanest default shape for many real apps.

A good first R2 example teaches both the binding and the delivery boundary: the worker decides what the browser gets.

Config focus: Direct bucket naming
Runtime shape: Get an object from R2 and stream it through a route
Best use: Private file delivery or media endpoints

Start by wiring the binding clearly in config

Minimal R2 config

import { defineConfig } from 'devflare/config'

export default defineConfig({

name: 'r2-example',

files: {

fetch: 'src/fetch.ts'

bindings: {

r2: {

FILES: 'private-files'

}

})

Then use it in one honest runtime path

This route pattern keeps auth, caching, and content-type decisions in your app instead of in an assumed bucket URL contract.
If you later choose a public bucket, make that an explicit architecture decision rather than a hidden side effect.

Serve an object through the worker

import { env } from 'devflare'

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

const url = new URL(request.url)

const key = url.pathname.replace(/^\/files\//, '')

const object = await env.FILES.get(key)

if (!object) {

return new Response('Not found', { status: 404 })

}

return new Response(object.body, {

headers: {

'content-type': object.httpMetadata?.contentType ?? 'application/octet-stream'

}

})

}

Lock in the behavior with one small test or smoke path

A better first instinct than “just use the bucket URL”

Routing through the worker teaches the real boundary between stored objects and browser-facing responses.

A quick route-level check

import { afterAll, beforeAll, expect, test } from 'bun:test'

import { createTestContext, cf } from 'devflare/test'

import { env } from 'devflare'

beforeAll(() => createTestContext())

afterAll(() => env.dispose())

test('GET /files/hello.txt serves the stored object', async () => {

await env.FILES.put('hello.txt', 'hello from r2')

const response = await cf.worker.get('/files/hello.txt')

expect(await response.text()).toBe('hello from r2')

})

Testing R2

R2 is local-friendly, which means you can test real object operations without inventing a storage adapter just to get off the ground.

Durable Objects

Devflare treats Durable Objects as a real first-class surface in config, local runtime, and tests, not as an awkward plugin hanging off the side of the worker.