Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(deps): update dependency dexie to v3.2.2 - autoclosed #121

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 30, 2020

WhiteSource Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
dexie (source) 3.0.1 -> 3.2.2 age adoption passing confidence

Release Notes

dfahlander/Dexie.js

v3.2.2

Compare Source

Security fix

Prohibit possible prototype pollution in Dexie.setByKeyPath() (dexie/Dexie.js@1d655a6)

Bugfix

Fix #​1473 Cannot use Dexie in react-native

A corresponding release 4.0.0-alpha.3 contains the same fixes for 4.x.

v3.2.1

Compare Source

  • Workaround for issue #​613: Automatically reopen IndexedDB connection in case it was unexpectedly closed, and redo the operation. When a transaction couldn't be created due to invalid state, Dexie will reopen the IndexedDB connection and retry creating the transaction.
  • Resolves #​1439 and #​1369 by extending the "exports" field to include "require" compliant version of dexie.

v3.2.0

Compare Source

### Dexie.js has become Reactive

After one year in alpha, beta and RC, Dexie.js with liveQuery() is now officially released. The main reason for this new feature is better integration with frontend libraries like React, Svelte, Vue and Angular.

Together with this release, the website https://dexie.org also got a face lift with tutorials for React, Svelte, Vue and Angular.

dexie.org

Take a look past the updated website. Old tutorials are replaced with modern relevant framework specific ones. We've added React, Svelte, Vue and Angular samples on the landing page.

All changes since 3.0.3 in chronological order

  • PR 1104: dbName follows dependencies.indexedDB (II)
  • Option {allKeys: true} to bulkPut() and bulkAdd() will be equally fast as not providing that option.
  • Code cleanup and optimizations.
  • Expose IDB 'close' event: Expose close event dexie/Dexie.js#1212
  • BulkError: Possible to track individual errors. Add failuresByPos property: BulkError: Add failuresByPos property dexie/Dexie.js#1209
  • Dexie.getDatabaseNames(): Small optimization for our workaround for non-chromium browsers lacking the IDBFactory.databases(). commit.
  • Argument to on.ready() callback will get a special Dexie instance that is not blocked (vip Dexie). This was the case also before but then we had to rely on zone state. This change makes it possible to perform non-dexie operations in on.read() callback (such as fetch()), loosing the zone state (PSD) but still have VIP access to the Dexie instance. This makes the code in a on.ready() callback not having to deal with wrapping all non-Dexie calls with Promise.resolve().
  • Allow multiple calls to Version.upgrade() on the same version - will run all of them instead just of the latest registered.
  • Retiring old workaround for safari 8 bug not allowing array argument to IDBDatabase.transaction().
  • Dexie.delete() specifies an empty addons list to ensure no addons are involved when deleting a database using that static method.
  • Minor extended the DBCore interface to make it possible for Dexie Cloud to sync certain operations consistently. Specifically, middlewares that implement the DBCoreTable.mutate() endpoint now also gets information on the where-critera and the update specification when originating from Collection.modify() or Collection.delete().
  • Support for Chrome's transaction durability option in Dexie constructor. PR #​1367
  • Official event Dexie.on('storagemutated')
  • Typings: Stop exporting Dexie as namespace. Enables VSCode's ergonomic auto-import feature for dexie. The namespace export was not even working as expected. The intent had been to support those that code Typescript without using modules. But even they must have been disappointed because the typings did not only reveal parts of the Dexie API.
  • Let liveQuery() be type-wise compable with RxJS (PR #​1417)
  • Switch to JS implementation of indexedDB.cmp() (PR #​1412)

Fixed Bugs since 3.0.3 in chronological order

  • #​1195 The 'update' crud-hook interpreted array properties as object with number keys.
  • #​1280 Cannot add CryptoKeys to table with auto-incrementing primary key
  • Typing correction: Fix version signatures (PR #​1287)
  • Fix #​1236 - problems updating FileSystemFileHandle properties.
  • Bugfix: Transaction.abort() does not rollback changes (filed as a repro PR in #​1329). Fixed in PR #​1330.
  • Bugfix in Virtual Indexes (the reuse of compound indexes as plain indexes): Couldn't reuse parts of primary keys - only parts of indexes.
  • PR #​1379 fix(bulk-delete): correctly define keys type. Fixes #​1364.
  • Bugfix for #​1381 Collection.delete() fails silently for queries on virtual indexes that use .filter().
  • Deleting multiple tables in a new version using null (#​1418)
  • (Another) mysterious MissingAPI error (#​1400)

v3.0.4

Compare Source

v3.0.3

Compare Source

Changes since 3.0.2

This release contains fixes that improves error resilience, typing correctness and bug fixes for some edge cases.

Typing fixes

  • Fix Table.bulkGet return typing to include undefined #​1098
  • Allow readonly arrays for bulk put & get methods #​1106
  • Use error keys insted of values for typescript #​1115

NOTE: Conditional types is now being used in dist/dexie.d.ts. If you are on an ancient typescript version (below 2.8) you will need to update typescript in your dev deps!

Improvements

  • Verify schema on open #​1108
  • Repro + resolve issue #​1112: typescript declaration of id makes autoInc fail #​1119
  • #​1136: Allow declaration-only tables for TS users

Bugfixes

  • Allow middleware hooks to return objects that contained field names that contain dotted strings #​1130
  • Resolve #​1127 #​1131
  • #​1146: Resolve #​1145 Regression: SchemaError during version upgrade
  • Bugfix of #​1154 (PR #​1155): WhereClause.equals(undefined) should fail, but it does not fail in dexie 3.0.0-3.0.2. It behaved correctly in dexie 2.x so it's a regression. It is important that libraries fail on invalid arguments so that subtle application bugs are nailed down more easily.

Addons

  • Issue 1048 Typings of addons for Dexie 3.0 #​1117
    The addons are released with the "next" tag on npm, so please test them and help me verify that #​1048 is solved:
    npm i dexie-observable@3.0.0-beta.9
    npm i dexie-syncable@3.0.0-beta.9
  • #​1138: Dexie.Observable: startObserving function: remove read-only query in order to avoid TransactionInactiveError
  • Bugfix of #​1148 (PR #​1149).

v3.0.2

Compare Source

PRs:

  • #​1062: Typing fix for Dexie.Observable IDatabaseChange.
  • #​1081: Run reading hooks in bulkGet
  • Updated dev-dependencies

Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by WhiteSource Renovate. View repository job log here.

@renovate renovate bot changed the title fix(deps): update dependency dexie to v3.0.2 fix(deps): update dependency dexie to v3.2.1 Feb 23, 2022
@renovate renovate bot changed the title fix(deps): update dependency dexie to v3.2.1 fix(deps): update dependency dexie to v3.2.2 May 16, 2022
@renovate renovate bot changed the title fix(deps): update dependency dexie to v3.2.2 fix(deps): update dependency dexie to v3.2.2 - autoclosed Jun 18, 2022
@renovate renovate bot closed this Jun 18, 2022
@renovate renovate bot deleted the renovate/dexie-3.x branch June 18, 2022 19:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant