David Fahlander

No, not unless you use indexedDBShim in node and sync it with indexedDB in browser.

There isn't today, but I have started writing a paging middleware that I want to introduce in a later version of Dexie. But as of now, one has to be...

The code for it was dry-coded in the branch [dexie-core](https://github.com/dfahlander/Dexie.js/tree/dexie-core) where built the middleware architecture DBCore that is now part of 3.x-alpha. But in that branch I also added a...

Unfortunately, paging support is not implemented, but instead of a new paging API, the idea is that the cache will assist in optimizing simple offset().limit() requests for paging. It's in...

Is there any other dexie addons or middlewares active? Are you experiencing the same issue on dexie@3 or only with dexie@4?

Could you try with dexie@3 and see if you experience the same issue?

How does the non-working package.json look? When I look at current one, it has ``` "production": { "module": "./import-wrapper-prod.mjs", "import": "./import-wrapper-prod.mjs", "require": "./dist/dexie.min.js", "default": "./dist/dexie.min.js" }, ``` Seems identical?

Tried to reproduce just now: https://github.com/dfahlander/dexie-vite-starter I get it working with a clean vite project with typescript / react and adding dexie and using dexie-react-hooks, But I saw there was...

If we do, nextjs apps suffer from double instanciating the dexie module (for some reason) and that causes problems as it has static properties that must be singleton instance. Ideally...

Thanks for this finding. Not sure how to properly proceed though. The path dist/dexie.min.js is expected to be there by other docs and samples, for example when including dexie in...