David Fahlander

sorry, it should be "jsnext:main", not "esnext:main".

Related to https://github.com/dexie/Dexie.js/issues/1439. But the only working solution is to export an ESM version of this addon. Even though this particular error would go away if upgrading dexie to 3.2.1-beta.2,...

From my part, the issue has been resolved. First of all I found other ways of deploying the node app - via az command line. Secondly, the state that trigger...

This is expected result if a mutation happens while the query is being executed. Since new mutations that can affect the query has occurred, the observable will not emit the...

Just got curiosity - why are you using Dexie.waitFor() in this case? That function is only useful when awaiting native promises (from things like webCrypto or fetch). In this case...

Thanks! Dexie detects the changes but angular fails to re-render when the observable emits a new value if the change originates from another tab. The reason is most probably that...

If I understand you correctly, you want to fetch data and update IndexedDB on scrolling below some point. * If no new email has arrived, the fetched data would be...

# useLiveQuery() with offset and limit Using offset/limit is also fine. As shown in some of my samples, you can use a react prop or state in your query, such...

Hi! liveQuery() computes whether a mutation would affect the query or not. It does not compute which parts of the result that needs to be refetched. Whenever a certain query...

@anurasin The tests are not comparable as the native-indexedDB version runs them in a single transaction and the dexie-based test in your zip does not create a transaction but runs...