search

Niek / chatgpt-web

ChatGPT web interface using the OpenAI API
https://niek.github.io/chatgpt-web/
GNU General Public License v3.0
1.85k stars 464 forks source link

Bump dexie from 4.0.1-beta.6 to 4.0.1-beta.14 #432

Closed dependabot[bot] closed 6 months ago

dependabot[bot] commented 7 months ago

Bumps dexie from 4.0.1-beta.6 to 4.0.1-beta.14.

Release notes

Sourced from dexie's releases.

Dexie v4.0.1-beta.11

Minor fix: Since 4.0.1-beta.10, we're allowing argument { disableAutoOpen: false} to db.delete() (not yet in docs), but it still failed if doing it.

Dexie v4.0.1-beta.10

Fixed bug introduced the recent release dexie@4.0.1-beta.7

  • Support for bfcache (to resolve #1776) had an issue that pagehide event resulted in closing down Dexie instances to a state where they did not auto-open again on pageshow.
  • The closing of connections happened no matter if event was a true bfcache event or not (didn't check the persisted property correctly)

Other

  • Fixed #1883 Exception when having nested index and inserting null value of nested parent.
  • Removed workarounds for IE11 as we are not supporting IE11 anymore

Dexie v4.0.1-beta.9

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: dexie/Dexie.js#1806)
  • 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)

dexie-export-import@4.1.1

  • Bugfix: dexie-export-import@4.1.0 was missing types (#1900)
  • Support for skipTables option to export and import (#1896)

v4.0.1-beta.8

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

... (truncated)

Commits


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
dependabot[bot] commented 6 months ago

Superseded by #438.