I really love the idea behind itty-durable and was wondering if this is something that you guys plan to maintain in the future?

Is it usable/stable right now for basic documented functionality?

It seems like state is automatically persisted, and I didn't manage to use persistent storage. I just want to make sure, if it's so then this should be in readme.

The README header images for all of the itty * repos make it very hard to read the second word if Github is set to dark mode.

See:

https://share.getcloudapp.com/QwuALvOp

In a durable object, the proxies overwrite the stubs on state. This will allow a durable object to still be able to create new ids and convert id strings to id objects for use in Proxy.get(id).

const stub = this.state.env.Counter;
const newId = stub.newUniqueId();
const idObj = stub.idFromString(storedObjectId);
this.state.Counter.get(newId).increment();
this.state.Counter.get(idObj).increment();

This is needed for creating fan-out systems or connection pooling like https://github.com/cloudflare/dog/.

in README.md

// get get the durable itself... returns json response, so no need to wrap

should be:

// get the durable itself... returns JSON response, so no need to wrap

I believe this line in the example code in the README:

// reset the durable)
.get('/reset', ({ Counter }) => Counter.get('test').clear())

should be:

// reset the durable
.get('/reset', ({ Counter }) => Counter.get('test').reset())

Please also note the removal of the extraneous ) at the end of the comment.

Having an example that shows setting the default state would also be helpful in relation to .reset().

I am trying to set up durable objects and when I try to get the JSON to return a modified response of an object it does not give me the parsed response even though I set the parse option to true.

Allows speed readers like me to more quickly assess if this repo is worth even reading. (Seems awesome, but I look at 20 repos/day & 5 blog posts, so 'reading' is a luxury.)

Some 'English as Second Language' folks might not understand fire = run.

Keep up good work!

I'm using itty durable and manually creating a proxyDurable the following way:

export const initAccountNodeByName = async (
  name: string,
  durableObject: DurableObjectNamespace
) => {
  const proxy = await proxyDurable(durableObject, {
    name: 'account',
    class: Account,
    parse: true,
  })

  const node = proxy.get(name) as Account
  return node
}

Everything works great but in the logs there the following errors occurs.

YN0000: { text: '' }
➤ YN0000:  Trace: 
➤ YN0000::     at Request.json (/Users/adrianmaurer/Code/kubelt/node_modules/undici/lib/fetch/body.js:392:17)
➤ YN0000: :     at runNextTicks (node:internal/process/task_queues:60:5)
➤ YN0000: :     at processImmediate (node:internal/timers:442:9)
➤ YN0000: :     at process.topLevelDomainCallback (node:domain:161:15)
➤ YN0000::     at process.callbackTrampoline (node:internal/async_hooks:128:24)
➤ YN0000: :     at Request.json (/node_modules/@miniflare/core/src/standards/http.ts:333:18)
➤ YN0000:      at withContent (/node_modules/itty-router-extras/middleware/withContent.js:1:132)
➤ YN0000: :     at Object.handle (//node_modules/itty-router/dist/itty-router.min.js:1:590)

note: this does not break the app but it's strange that the proxy object is returning an empty string response.

Here is the DO:

export default class Account extends createDurable({
  autoReturn: true,
  autoPersist: false,
}) {
  declare state: Node.IttyDurableObjectState<Environment>

  async getProfile(): Promise<Profile | null> {
    const stored = await this.state.storage.get<Profile>('profile')
    return stored || null
  }

  async setProfile(profile: Profile): Promise<void> {
    return this.state.storage.put('profile', profile)
  }
}

Why

Having a default method or property on the DO proxy to reflect the DO object id is useful

What

Expose the object id in a property or method. Example

myDo.$.id

or

myDo.getId()

I would be nice to access the this.state.storage object in the proxy object.

Why?

I've migrated to itty-durable from a standard DO. Itty-durable property proxy stores everything in a data property so I can t access my existing data properties. The storage object is there but is not exposed via types so I have to ignore the type checker and do a run time migration.

Proposal

A) If storage is not meant to be exposed don't store everything in a single data object. Or B) expose storage by typing state argument with DurableObjectState https://github.com/kwhitley/itty-durable/blob/v1.x/src/itty-durable.js#L20

The transformResponse fails for invalid JSON. Because it wasn't async, it would always return the promise from the response.json() call. Making it async allowed it to fail the JSON and move on to the next step, but because the body was already read/parsed, the response.text() would always fail. So we have to read the text first, then try and parse it as JSON. If it is JSON, return it. If not, return the text. If reading the text failed, return a response.