David Fahlander

Dexie uses BroadcastChannel to communicate mutations between tabs and workers. I see no reason why a web worker would not be able to consume liveQueries as long as the browser...

Hooks and middlewares can affect what is being stored, while liveQuery observes what has already been committed to the database. That is the logical reason why hooks and middleware can...

The existing BroadcastChannel event 'x-storagemutated-1' can be listened and reacted to if you want to go one level deeper than what liveQuery(). The event name is stable as its data...

> because the tx may be cancelled or fail downstream? Yes > will i need to be on alpha for all that? No, 3.2.x is ok. > i managed to...

Thanks. Trying to understand your goal with the question. So here are some questions for you: What are you trying to achieve? Do you want to display some progress to...

*EDITED* db.on('ready') is invoked **after** upgrade transaction has completed. But if your upgrader calls non-dexie async calls such as fetch(), webcrypto calls etc, the upgrade transaction will commit too early...

No, only use Dexie.waitFor() to do things outside Dexie. If you access the upgrade transaction in there, you will have a deadlock. Only use waitFor around non-indexeddb work such as...

I don't feel comfortable with this. If BroadcastChannel isn't working when cookies are disabled, changes are that neither IndexedDB or localstorage works either. Taking care of this scenario needs a...

@DjakaTechnology NextJS will compile all your components under pages for both frontend and backend (node-based). The dexie-export-import addon probably fails when required from the backend because it was written for...

Closing this issue. Dexie is supported in both web workers, shared workers and service workers (since many years ago). This issue was about how to import it, which is more...