Keep bridge architecture documentation behind advanced/internal links
The bridge architecture document remains valuable, but it should not be on the first-hour developer path.
Link the bridge architecture doc only from advanced runtime, transport, or maintainer pages. Beginner docs should show recipes first and link internals after the developer already has a working example.
- Canonical file
- Audience
- Maintainers and advanced runtime debugging
- Linked from
- Transport and project architecture docs
Read this after the recipe path works
- You are debugging the bridge transport or local runtime startup.
- You are changing how local RPC, Durable Objects, service bindings, or framework platform glue cross the worker boundary.
- You need maintainer context, not first-run setup instructions.
A bridge-backed value that needs a transport file
export class Money {
constructor(
readonly amount: number,
readonly currency: string
) {}
format(): string {
return new Intl.NumberFormat('en-US', {
style: 'currency',
currency: this.currency
}).format(this.amount)
}
}
Previous
Project Architecture
This is the practical answer to “what does a real Devflare project look like on disk?” — from a small worker package, to a multi-surface app, to a hosted SvelteKit package, to a Bun monorepo with several deployable workers.
Next
Routing
Use for request-wide behavior, for leaf handlers, and when you need a custom root, prefix, or route-only app.