David Fahlander

Dexie.Observable uses storage event to propagate changes across browser frames. This event is not present in workers, so it cannot detect changes as fast. However, it should instead do an...

You also need to import dexie-observable from the sw

Sorry, missed that you already do that.

The producer must also have dexie-observable imported. For example if your writes occur in a browser window, dexie-observable will make sure the changes are propagated to the _changes table so...

I cannot see why these two syntaxes would do any difference as the db returned via promise from Dexie.open() will be the exact same instance, which would have had observable...

In [[email protected]](https://github.com/dfahlander/Dexie.js/releases/tag/v3.1.0-alpha.4) you get built-in observability in Dexie including propagation across tabs and workers. [See live example](https://stackblitz.com/edit/dexie-todo-list?file=components%2FTodoListView.tsx)

This happens when you execute a transaction and await non-Dexie calls within it. ```js await db.transaction('rw', db.myTable, async () => { await fetch('https://xyz.org/...'); // Here's a problem: awaiting non-dexie call...

Are you using a very old browser or Internet Explorer, Legacy Edge or very old version of some other browser?

These type of problems occur on very old browsers - but also when using IndexedDBShim or possibly also fakeIndexedDB instead of using the native IndexedDB in the browser. One workaround...

Check if IndexedDBShim is included. Try remove it. If you'd still need IndexedDBShim, make sure to transpile the code to ES2016 or ES2015. No problem with your English :)