What is durable objects?

@User your example itty-durable doesn't work for me, I get

"message": "Uncaught ReferenceError: withDurables is not defined\n  at line 1\n  at line 1 in r\n  at line 1\n  at line 1\n"

I think it just needs the import updated though?

oh geez, yeah add the

import { withDurables } from 'itty-durable'

how embarrassing 😅

btw, I think I may change from extending a base class to a wrapper function to enable this functionality on the DO... stealing this from @User thanks to a convo this morning :p - means I can ditch the class factory function as well (the wrapper can just take options), and lets people keep their DO 100% pure for things like unit tests

i can proxy trap it all the same, allowing for all the same interface/lack-of-code

@User updated README https://www.npmjs.com/package/itty-durable

I'm working on a library to make it easier to communicate with durable objects in the browser by making them feel like a local instance. Does anyone have a use case for this? I would love to hear about it. cc: @matt

My goal is to land somewhere between Comlink and Firebase

I'm really hoping his library can just do everything mine does and better, so I can pass the torch entirely 😅

no pressure @User 🙂

sounds interesting! I like the idea of extending the object stub to something you can use from the client and it feels like you're talking directly to a DO.

as always, the challenge will be reducing network round trips

one challenge w that @User - now you'd want to include authentication within your DO to take browser requests directly, rather than piping them through a gateway Worker that handles auth

(at least where auth is required)

you're always going to go through a normal worker to hit the DO, they can't service HTTP requests directly (i.e, have a route assigned to them)

@User I get

"message": "No event handlers were registered. This script does nothing.\n"

Yeah I'd think all of that would be handled in your worker (re: auth)

Hi folks, while playing around with DO I'm currently stuck at

fetch

not being passed anything in it's

env

argument. I `JSON.stringify`'ed it for debugging purposes and it's indeed just an empty object. Any ideas what could be wrong?

I'm referring to the main exported

fetch

, like here: https://github.com/cloudflare/durable-objects-rollup-esm/blob/master/src/index.mjs#L8

@User what are you expecting to be there? Do you have config vars/kv namespaces or similar set in your wrangler.toml?

I have a

durable_objects

binding in my

wrangler.toml

and would have expected to be able to access it via

env

Like in this example: https://github.com/cloudflare/durable-objects-rollup-esm/blob/master/src/index.mjs#L18

@User are you using wrangler environments

jup

the

[durable_objects]

section is not inherited -- you'll need to provide it for each environment as a subtable of the environment, like

[env.staging.durable_objects]

that's it, thanks!

Was able to get my counter thing working with the help of @User , thanks so much!

Does anyone know how to do crons with ES6 modules? I don't think this is working: export default { fetch: router.handle, --> working scheduled: cronHandler, --> not working }