fix: bump dexie-observable from 3.0.0-beta.11 to 4.0.0-beta.13

[dependabot[bot]]

Bumps dexie-observable from 3.0.0-beta.11 to 4.0.0-beta.13.

Release notes

Sourced from dexie-observable's releases.

Dexie v4.0.0-alpha.4

• Fix for #1576 Node.js process not exiting when Dexie.js is imported
• PR #1559 Support for FileSystemDirectoryHandle when cloning

Dexie v4.0.0-alpha.3

Security fix

Prohibit possible prototype pollution in Dexie.setByKeyPath() (https://github.com/dexie/Dexie.js/commit/1d655a69b9f28c3af6fae10cf5c61df387dc689b)

Bugfix

Fix #1473 Cannot use Dexie in react-native

A corresponding release 3.2.2 contains the same fixes for 3.x.

Dexie v4.0.0-alpha.1

The initial release on 4.0. Currently pretty much identical to 3.2.1+ but with:

• More precise typings for Collection.modify() and Table.update() using template literal types for keyPaths.
• Typings: Table.add() and Table.put() won't require methods to be present on the object to add. Allows for adding POJO objects rather than having to construct the full class to add a row.
• Typings of Table generic: A property name can be used as 2nd generic argument (TKey) rather than the direct type. This will infer the key type from the type of that property and make it optional in Table.add() and Table.put() (see sample below)
• New class exported class Entity that can be optionally used as a base class in order to resolve dependency issues when mapping tables to classes. A subclass of Entity has a private property this.db which is the Dexie instance it originates from. Entity subclasses are not meant to be constructed by application code.

  
  export class Friend extends Entity<FriendsDB> {
    id!: number;
    name!: string;
    age!: number;
  birthday() {
  return this.db.friends.update(this.id, friend => ++friend.age);
  }
  }
  export class FriendsDB extends Dexie {
  friends!: Table<Friend, 'id'>;
  constructor() {
  super("FriendsDB");
  this.version(1).stores({
  friends: '++id, name, age'
  });
  this.friends.mapToClass(Friend);
  }
  }
  

Dexie v3.2.3

Bugfixes:

... (truncated)

Commits

• See full diff in compare view

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 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)