Is there any reason I'd be getting "internal error" when trying to connect to a DO? I saw this the other day, but it was super late at night so I just called it a day and it was fixed by the morning, but I'm getting it again now.

Yeah, you should be able to call

this.constructor.name

from inside the DO unless i'm mistaken...

Depending on whether your code is minified though, that may not work.

actually it's confirmed, I literally put that in my code a few min ago... haha

excellent point - mine currently isn't

message has been deleted

(overrides will be available)

message has been deleted

What do you mean exactly by Q2?

with example DO:

with timestamps enabled, it would get initalize with

{ counter: 0, created: new Date }

and updates would add

{ modified: new Date }

with that, calls to

increment()

would bump the

{ modified }

prop, and calls to

add(a, b)

would not (no change to log)

So regarding what will be published here in a few minutes... it'll be a DO base class (with factory for constructing base class with diff options), with middleware (for

itty-router

) that allows for usage like this in your Worker:

Note, we've thrown out async setters (for now) entirely... gotta use methods to execute on the DO, or props/toJSON for reading

and see the actual DO code just above this in the thread

I'll try to record a screen cast explaining how it works - in the hopes that it inspires someone to come up with something even better 🙂

you'll have the option of accessing methods on the stub directly (as shown) or using the

.fetch(request)

on the stub manually and adding your own router flow to the durable (powerful for chained request behavior or more elaborate calls)

awesome

i like the option of magic timestamps, but not by default

Is there a way to get Workers Sites workers to play nicely with DOs?

[site]

configuration in wrangler.toml doesn't seem to support

upload_format="modules"

also is there a reason Sites are configured separately from workers? the only difference seems to be a

bucket

option that uploads static assets to KV. I could imagine this being useful even for non-sites

guess i should be asking in wrangler channel

you using the

@cloudflare/wrangler@beta

?

although to be fair, I def haven't tried to integrate w Sites

Heads up all - I've released the super-early prototype of

itty-durable

https://www.npmjs.com/package/itty-durable This is a pretty tight coupling of itty-router and a durable base class (to extend) to remove nearly all DO boilerplate. Docs are sparse for now, and I apologize, but I'll rapidly move to flesh that out... any questions I'd recommend asking here (if not too lengthy as I already take up too much thread space here ;), on Twitter, or in GitHub issues on the repo itself. Really looking for early feedback on the usage, the interface, etc.

I'm trying to do something similar to this rn

using https://github.com/cloudflare/wrangler/releases/tag/v1.15.0-custom-builds-rc.2

@luke @Kevin W - Itty , Workers Sites doesn't work with the current release of wrangler beta. I wrote some PRs to add support (which have just been merged in), but they haven't been published as a new release yet. Check out #818615097731317802 for more info.