Igor Gassmann

We also want to check if journal files get properly deleted by the [clean up process that deletes old state db files](https://github.com/livestorejs/livestore/pull/569).

@kitten, thanks for the fix! :) **Small thing missing**: As mentioned in the issue description, the JSDoc for the configuration property is also outdated: https://github.com/expo/expo/blob/55ca495d26b2e6f106783fd0cf1af5c5328f4a53/packages/babel-preset-expo/src/index.ts#L102-L103

Hey @Nick-Motion! Thanks for reporting this issue. I suspect your problem is the same as the one described in https://github.com/livestorejs/livestore/issues/256. Could you please provide a reproduction so I can confirm...

@oskargotte I believe that's possible, yes. Feel free to open a PR with the change.

Hey @BRKalow! Unfortunately, this doesn't solve our use case because we do have URLs in the following format: - `/events/page.viewed` - `/events/user.signed.up` Our event names follow the dot case notation...

The [multi-store API](https://docs.livestore.dev/reference/framework-integrations/react-integration/#multi-store) provides some foundational primitives for store management (StoreRegistry tracks stores, lifecycle management, etc.), but doesn't include the persistence-layer inspection and cross-adapter discovery features requested here.

Update: The [multi-store API](https://docs.livestore.dev/reference/framework-integrations/react-integration/#multi-store) is now the recommended way to use multiple stores, but the worker overhead problem still exists.

@slashv @schickling Is this completed now that https://github.com/livestorejs/livestore/pull/753 has been merged?

The [multi-store API](https://docs.livestore.dev/reference/framework-integrations/react-integration/#multi-store) provides `registry.preload()` for pre-loading stores: ```ts await registry.preload(storeOptions({ storeId: 'issue-abc123', schema: issueSchema, adapter, })) ``` This addresses the orchestration layer for pre-loading multiple stores, but still uses...