As far as I know, what you are wanting is how synced works currently. Here is a demo that shows the synced event firing consistently when the doc loads:

https://codesandbox.io/p/sandbox/y-indexeddb-updates-test-forked-6mf9xl

Feel free to fork that sandbox to create a reproducible demo of the problem you're experiencing.

@raineorshine thanks for the quick reply and providing the sandbox link, I will try to replicate it there.

For reference the event does fire consistently however for the same document the handler will sometimes show empty content on that event. Is it possible that there is a race condition between that event being fired and the content being available to read in the ydoc object?

perhaps I also misinterpreted the README and specifically this wording:

The event is also fired when no content is available yet.

This seems to suggest that content will be available after that event is fired

The synced event will only fire after all updates have been read from IndexedDB and applied to the YJS Doc.

Given this, I interpret the README to mean that the synced event will still fire even when no doc exists in IndexedDB with the given name.

After more investigation I can confirm that the issue was elsewhere. I must admit I did jump to conclusions after seeing yet as part of

The event is also fired when no content is available yet.

thinking that the content would somehow be loaded or available after the event was fired

Great, I'm glad you got to the bottom of it.

I agree the language is ambiguous. If you have the time, please consider opening a PR to change the wording so that others do not experience the same confusion.

@raineorshine sorry it took me so long to make this propose this simple change but here it is: #37

Hi @ben-bourdin451 what issue were you running into? I am also seeing the 'synced' event fire twice, once before the existing updates are applied and once after. Wondering if this is similar to what you experienced.