Why deprecated? What to use instead?

[josephbuchma]

Just stumbled into itty.dev - looks great!
I see that it's deprecated in the docs, but there is no information what to use instead. Can you please point me in the right direction?

[kwhitley]

Hey Joseph!

Itty durable is still fully functional, but only with the pre-RPC Durable Objects. While we kinda showed what was possible, Cloudflare (after a few years) eventually wrote a pretty killer true-RPC system. itty-durable@next was an initial stab at a rewrite over the new system. It's much leaner (only about 400 bytes), brings a flexible storage system (defaulting to their own, but allowing you to save/restore from external data stores), etc.

https://www.npmjs.com/package/itty-durable/v/3.0.0-next.3

If you're using newer Workers, I'd recommend starting there if interested.

[josephbuchma]

Thank you @kwhitley

BTW, have you ever ran into this error?

Cannot access MyDurableObject#myMethod as Durable Object RPC is not yet supported between multiple wrangler dev sessions.

I fond only this relevant issue: cloudflare/workers-sdk#5918
But I'm not running multiple wrangler dev instances. Not sure what I'm doing wrong, but will try itty-durable v2 again, or just fetch manually.

[josephbuchma]

Ok, I figured it out. Setting script_name property for the DO binding in wrangler config was causing the trouble.
This is not mentioned anywhere, but I decided to just try to get rid of that property after reading this section:

https://developers.cloudflare.com/durable-objects/platform/known-issues/#development-tools

Specficially:

wrangler dev has read access to Durable Object storage, but writes will be kept in memory and will not affect persistent data. However, if you specify the script_name explicitly in the Durable Object binding, then writes will affect persistent data. Wrangler will emit a warning in that case.

So it works as long as state is not persisted.