This is the last planned release in the series of small releases on the 4.0-track. The goal is to get a stable 4.0 release as soon as possible, but I'll wait to see some reports from usage before moving on.

Isolate readwrite transactions from live queries (#1881)

• Don't let dexie4's new cache get optimistic updates from explicit 'rw' transactions since it breaks isolation. Still, let "transaction-less" operations (no explicit transactions from user code) shine immediately through to liveQueries if cache isn't disabled in the constructor options.
• This makes dexie 4 behave exactly like dexie 3 when transactions are used, but may still optimize common liveQueries using the cache.
• Still, if there are 10 identical liveQuery subscriptions on a page, only one of them will need to requery IndexedDB after a write transaction and the other 9 will get their values from the cache. This is also the case after an explicit 'rw' transaction has committed.

Improved debugging experience (#1879)

• We're using Chrome's Async Task Tagging API to track failing operations down to the app code that initiated the operation. As long as Dexie.debug = true, we will print out call stacks in the console for any failed operation where the application code that initiated the operation is visible in the stack trace, no matter if the operation had to go through a bunch of async jobs before failing, such as implicitely opening the db in the backround, run some upgraders etc, while the only thing the user code did was a simple operation such as db.friends.get(1), but since it triggered a db open in the backround led to all these background work being performed. Before these situations were hard or almost impossible to track down to the application code.
• Fail fast on table.get(undefined) (To avoid unreadable call stacks like this: https://github.com/dexie/Dexie.js/issues/1806#issuecomment-1884977367)
• Remove old proprietary "long stacks" support that was tailored for older browsers and have no gain anymore.

Optimizations

• #1821 liveQueries of the form db.someTable.orderBy('id').primaryKeys() won't be affected by a property change on an object of one of the observed keys, since the keys don't change. Only object adds and deletions will trigger the query to update.

Typings

• Use TInsertType in Table.update and Collection.modify (#1764)

[email protected]

• Bugfix: [email protected] was missing types (#1900)
• Support for skipTables option to export and import (#1896)

NOTE: We're aiming for a stable 4.0 to be released as soon as possible. To get there, we're releasing new versions quite frequently now. Reason: splitting up major changes into smaller releases allows users to revert versions in steps rather than the whole version.

Changed Version Handling (See PR #1880)

• Dexie will now accept upgrading schema WITHOUT incrementing the version number
• Dexie will now be able to open a previous version of the database without complaining

Version numbering is now only useful when you need to:

• ...migrate the data (attaching an .upgrade() onto a version.
• ...delete tables

Other issues:

• Fix issue with BigInt64Array (#1890)

This is the first release in a series of small releases on the 4.0-track before it goes release candidate. Expect a few additional beta versions coming out soon. The goal is to get a stable 4.0 release as soon as possible.

Dexie Cloud

• Dexie Cloud Manager where you can purchase a production subscription, manage database login policy, describe your databases and view and upgrade individual users. Also possible to specify a custom SMTP settings to relay all OTP and invite emails.
• Latest version of dexie-cloud-addon is 4.0.1-beta.56.
• Allow database owners to troubeshoot issues that their users are facing. A database owner with full access to the all database content through the API or through npx dexie-cloud export can now also login to their app with " as " in the email field and get the OTP sent to their own email but be authenticated as the other user.
• Support {otp, otpId} as arguments to db.cloud.login(). The parameters must come from an OTP challenge. This will bypass the login dialog and directly authenticate the user. Usefule when customizing email templates to generate magic links with the otp and otpId as part of the query to the app.

Bugfixes

• #1863 useLiveQuery with multi-entry-index
• #1776 Support bfcache

dexie-export-import

• #1848 Support for transform option to export and import https://github.com/dexie/Dexie.js/commit/7fd94f00e74e039a7adf667cd75a782020939b6a

Other

• Expose the optional TInsertType of Dexie.Table generic: https://github.com/dexie/Dexie.js/commit/c94e9e8ef16cd4f687a1a2570705d277aa7646f9

[email protected]

• Don't patch Promise.prototype.then (#1293)
• Resolved #1858 'Entity' is not exported from 'dexie' (imported as 'Entity')
• Fixes to run on LambdaTest (#1752). The migration from Browserstack to Lambdatest is now complete.

[email protected]

• Resolved #1724: Allows plus signs in email address (in order to use a single email address act as multiple users for testing)
• Resolved dexie/dexie-cloud#4 - Automatically make "email" property of "members" lowercase and trimmed (avoid inviting members with different casing in email address)

• Resolved #1831 again: Make sure liveQueries always run in own macro tasks (7c13770ffc0b8cb1189921ee6d5b4c64c4654950)
• Resolved #1843: Avoid running dexie in double module instances (EMS module is now ESM wrapper around UMD module + detect and avoid double imports of dexie) fc572aa71a652e7c01b8bac81da6a242aef47e2c

[email protected]

[email protected]

Fixes #1837 - a bug in dexie-cloud-addon woken up when upgrading dexie to in 4.0.1-beta.2.

Recommended to:

• Upgrade dexie to [email protected]
• Upgrade dexie-cloud-addon to 4.0.1-beta.53

Replaced by Dexie v4.0.1-beta.4

Various issues fixed, summary:

• General stability (work around chrome issue + fix dexie issues)
• Vite experience with dexie-react-hooks
• Dexie Cloud developer experience

[email protected]

• Workaround for UnknownError in Chrome (issue #543)
• Dexie 4 optimistic updates are not reverted (issue #1823)
• Fixed "Readwrite transaction in liveQuery context" (issue #1831)
• Correction of Promise.finally (commit 09058eab1563d3b4eaee9c9dd3a9a03705bac132)

[email protected]

• Improved vite experience (commit 3ff7d50a1bb263dfd15370ee674b66cfd20fa3d3)
• Improved typing for usePermissions so that it can be used in plain interface typed tables Table<MyInterface> (commit 437b697ffa3582fbedc0a786572e93f4b2b3e422)

[email protected]

• Fix value of db.cloud.version (did not reveal the version of dexie-cloud-addon)
• Fixen an issue with source map (better debugging experience)
• Export types and helpers needed for customizing built-in OTP authentication (commit 241a76c1e4a9abb9743bd34c093505039a8bf944)

[email protected]

• Added missing declaration of Dexie.debug: https://github.com/dexie/Dexie.js/commit/27ce0212291595ffabc8498762f41343beb326b0
• Bugfix: Support single values compound keys: https://github.com/dexie/Dexie.js/commit/93ea5eb11121b2b3839cf3523ed55d41e7c1e387
• Bugfix: Provided tx argument to db.transaction() callback would not respect the transaction if db was vip. https://github.com/dexie/Dexie.js/commit/232517816530541359592d506005e0fa07d005f6
• liveQuery with cache enabled: signal subscribers outside the async context https://github.com/dexie/Dexie.js/commit/c6b40bdef620babbf2cd58d6cd59df9bf0086470

[email protected]

• Implementation of the new subscription model https://medium.com/dexie-js/dexie-cloud-subscription-model-cbf9a709ce7
• Updated dexie-cloud-todo-app sample with license eval expiration alert.
• Support for logout API instead of having to delete or clear the database: db.cloud.logout().
• Support for logging in another user without logging out the current one (in db.cloud.login())
• Other fixes and improvements of dexie-cloud-addon.
• Allow expired eval users to pull down data but not to push.
• Treat expired eval users as being forever offline (may still use app but without sync) until they are upgraded to prod by the database admin.
• Remove console logs from the production build.
• Default OTP GUI: Auto-submit OTP when 8 characters are pasted or written.
• Bugfix: Syncing failed if table had inbound compound keys (#1777)
• Handle API-Rate-limits gracefully, avoiding 429 responses by slowing down sync calls when less than 50% of remaining rate-limit are available. https://github.com/dexie/Dexie.js/commit/3c4e698464ca78c402a25b0ad4faeb539f0d4700 New dexie-cloud option: disableEagerSync

To install / upgrade:

npm i dexie@next
npm i dexie-cloud-addon@latest

PR #1766: Dexie Cloud stuck in login-phase if option {requireAuth: true} was used to db.cloud.configure()

The fix is generic in dexie libary for db.on('ready') callbacks so that the Dexie instance passed to the callback can be used without blocking.

Background:

When the on('ready') callback executes, the ready state shall still not be resolved because any on-ready subscriber's flow is part of making the db ready to resume application queries. But the callback itself need exclusive access before application queries resume - otherwise any db call will block like if it was an application-made db call. This works fine and has been working fine since dexie@2, but has been exclusively based on an async context that spans over the entire flow of db-on-ready callbacks. However, some on-ready callbacks (specifically dexie-cloud's) need to do calls outside of Dexie - such as fetch() calls - those calls will loose the AsyncContext and thus the exclusive access to the db. Therefore, we're now providing a Dexie instance as argument to the on-ready callback - an instance that can call dexie exclusively regardless of the async context. However, a bug prevented this from functioning properly until this release.