Simplifies usage of Cloudflare Durable Objects, allowing a functional programming style or class style, lightweight object definitions, and direct access to object methods from within Workers (no need for request building/handling). Heavily influenced by and loosely forked from https://github.com/kwhitley/itty-durable/ but smaller, more focused, and with TypeScript support.
- Removes nearly all boilerplate from using Durable Objects
- Exposes APIs to be called from Workers
- First class Typescript support
- Allows a functional programming style in addition to the object oriented style of Durable Objects
- Extends existing APIs rather than replacing them
export interface CounterAPI {
get(): number
increment(): number
add(a: number, b: number): number
}
export interface Env {
Counter: DurableObjectNamespaceExt<CounterAPI>
}import { createDurable } from 'durable-apis'
import { Env } from './types'
// Functional style, pass in a function that returns an object with callable API methods
export const Counter = createDurable(({ blockConcurrencyWhile, storage }: DurableObjectState, env: Env): CounterAPI => {
let counter = 0
let connections = new Set<WebSocket>()
blockConcurrencyWhile(async () => counter = (await storage.get('data')) || 0)
// Will return the current value of counter
function get() {
return counter
}
// Will return the current value of counter
function increment() {
storage.put('data', ++counter)
return counter
}
// Note that any serializable params can passed through from the Worker without issue.
function add(a: number, b: number) {
return a + b
}
// OPTIONAL: Handle any requests not handled by the API (avoid naming this `fetch` so we can still use the global
// `fetch` method in our durable)
function handleFetch(request: Request) {
if (request.headers.get('Upgrade') === 'websocket') {
const [ client, server ] = Object.values(new WebSocketPair())
server.accept()
connections.add(server)
server.addEventListener('close', () => connections.delete(server))
server.addEventListener('message', ({ data }) => connections.forEach(conn => conn.send(data)))
return new Response(null, {
status: 101,
webSocket: client,
})
}
return new Response(null)
}
// Only public-facing API will be exposed for calling from Workers
// Adding a fetch method will catch any requests not handled by the API, allowing for Websocket request handling, etc.
return { get, increment, add, fetch: handleFetch }
})import { getDurable } from 'durable-apis'
import { Env } from './types'
export default {
async fetch(request: Request, env: Env) {
const Counter = getDurable(env.Counter, 'test');
const path = new URL(request.url).pathname;
let count = 0;
if (path === '/') {
count = await Counter.get();
} if (path === '/increment') {
count = await Counter.increment();
} else if (/^\/add\/\d+\/\d+$/.test(path)) {
// expects /add/83/12
const parts = path.split('/');
const a = parseInt(parts[2]) || 0;
const b = parseInt(parts[3]) || 0;
count = await Counter.add(a, b);
} else else {
return new Response('Not Found', { status: 404 });
}
return new Response(JSON.stringify({ count }), { headers: { 'Content-Type': 'application/json' } });
}
}import { ThrowableRouter, missing, StatusError } from 'itty-router-extras'
import { withDurables } from 'durable-apis'
import { Env } from './types'
// export the durable class, per spec
export { Counter } from './Counter'
const router = ThrowableRouter({ base: '/counter' })
router
// add upstream middleware, allowing Durable access off the request
.all('*', withDurables())
// get the durable value...
.get('/', (req: Request, { Counter }: Env) => Counter.get('test').get())
// returns the value from the method
.get('/increment', (req: Request, { Counter }: Env) => Counter.get('test').increment())
// you can pass any serializable params to a method... (e.g. /counter/add/3/4 => 7)
.get('/add/:a?/:b?',
({ params: { a, b }}: Request, { Counter }: Env) => Counter.get('test').add(Number(a), Number(b))
)
// use fetch like normal when direct APIs aren't enough, such as when handling a websocket upgrade
.get('/ws', (req: Request, { Counter }: Env) => {
if (request.headers.get('Upgrade') !== 'websocket') {
throw new StatusError(426, 'Expected Upgrade: websocket')
}
return Counter.get('test').fetch(req)
})
// 404 for everything else
.all('*', () => missing('Are you sure about that?'))
// with itty, and using ES6 module syntax (required for DO), this is all you need
export default {
fetch: router.handle
}
/*
Example Interactions:
GET /counter => 0
GET /counter/increment => 1
GET /counter/increment => 2
GET /counter/increment => 3
GET /counter/add/20/3 => 23
*/import { DurableAPI } from 'durable-apis'
import { Env } from './types'
// If you prefer the Class style, use a class like you normally would, wrapping it in our durable handler.
// Note: all class methods are callable remotely using this method.
export class Counter extends DurableAPI<Env> {
counter: number
connections: Set<WebSocket>
constructor(state: DurableObjectState, env: Env): CounterAPI {
super(state, env)
this.counter = 0
this.connections = new Set()
state.blockConcurrencyWhile(async () => counter = (await state.storage.get('data')) || 0)
}
// Will return the current value of counter
get() {
return this.counter
}
// Will return the current value of counter
increment() {
this.state.storage.put('data', ++this.counter)
return this.counter
}
// Note that any serializable params can passed through from the Worker without issue.
add(a: number, b: number) {
return a + b
}
// OPTIONAL: Handle any requests not handled by the API (avoid naming this `fetch` so we can still use the global
// `fetch` method in our durable)
handleFetch(request: Request) {
if (request.headers.get('Upgrade') === 'websocket') {
const [ client, server ] = Object.values(new WebSocketPair())
server.accept()
this.connections.add(server)
server.addEventListener('close', () => this.connections.delete(server))
server.addEventListener('message', ({ data }) => this.connections.forEach(conn => conn.send(data)))
return new Response(null, {
status: 101,
webSocket: client,
})
}
return new Response(null)
}
}This library works via a two part process:
-
First of all, we create a function to implement your Durable Object (through
createDurable()). This embeds a tiny internal itty-router to handle fetch requests. Using this removes the boilerplate from your objects themselves, allowing them to be only business logic. Durable Objects defined on yourenvobject will be extended automatically the same waywithDurables()does inside Workers. -
Next, we expose the
withDurables()middleware for use within your Workers (it is designed for drop-in use with itty-router, but should work with virtually any typical Worker router, andextendEnv()can be used with no router). This replaces your stubs on theenvobject with extended versions of themselves. Using these extended stubs, you can call methods on the Durable Object directly, rather than manually creating fetch requests to do so (that's all handled internally, communicating with the embedded router within the Durable Objects themselves).
npm install durable-apis
Super class to create DurableAPIs. It creates a router and handles the fetch method for calling methods on the class. It stores the state and env property on it and updates env with extendEnv to extends DurableObject stubs to support calling methods remotely.
Factory function to create the DurableAPI function that wraps your API.
Note: if you're confused at how a function can replace a class, it is a simple quirk with how JavaScript treats classes. If something is returned from the constructor of a class, it is returned in the new Class() assignment. This means for a function myFunc() that returns a value, the two statements obj = myFunc() and obj = new myFunc() are equal.
Recommended middleware to extend Durable Object namespaces with an updated get() method on the env object. Using the new stubs returned allows you to skip manually creating/sending requests or handling response parsing.
If not using middleware, use this to extend the Durable Object stubs get() method on the env object with an updated version that will let you call API methods directly on the stub. Using these stubs allows you to skip manually creating/sending requests or handling response parsing.
The new get() method will still work the way it did before, taking a DurableObjectId and returning a stub that you can call fetch() on. But you can also call other methods on the stub which will be proxied to the Durable Object. In addition, if you pass a string to get() that is 64 characters long (the length of a Durable Object id), it will automatically convert that to an id object (using idFromString()) and return the stub. If you pass a string that is not 64 characters long, it will be treated as the name and converted to the id (using idFromName) before returning the stub. If you pass nothing, a new id will be created (using newUniqueId()) and the stub will be returned.
Typescript interface which will add the interface methods for T to the stub proxy. This allows Typescript users to define their env object with the specific APIs that their Durable Objects implement, helping avoid errors in code. The methods return types are all wrapped in Promises automatically if the method does not already return a Promise since calling a Durable Object will always be an asyncronous operation.
Thanks to Kevin Whitley for the Itty Router library and for work on Itty Durable which this was modeled after.