ethkr-controler - npm Package Versions

[9.0.0] [DEPRECATED]

Added

• Add support for keyring init method (#163).
  • If a keyring has an init method, it will be called automatically upon construction. It is called with await, so it can be asynchronous.

Changed

• BREAKING: Replace constructor option and public property keyringTypes with keyringBuilders (#163).
  • The constructor now takes keyring builder functions rather than classes. Each builder function should return a keyring instance when called, and it must have a type string property set to the keyring type name. See the newly exported keyringBuilderFactory function for an example. The builder functions must be synchronous; use an init method for asynchronous initialization steps.
• BREAKING: KeyringController is now a named export instead of a default export (#163).
• BREAKING: Update @metamask/eth-simple-keyring from v4 to v5 (#171).
  • This keyring type is included as a default. If you are using this keyring API directly, see the @metamask/eth-simple-keyring release notes for details on required changes.
• BREAKING: Replace getKeyringClassForType method with getKeyringBuilderForType (#163).
• BREAKING: Update @metamask/eth-hd-keyring to v5 (#177)
  • This keyring type is included as a default. If you are using this keyring API directly, see the @metamask/eth-hd-keyring release notes for details on required changes.
• BREAKING: Require support for ES2020 (#177, #180)
  • As a result of some dependency updates made in this release, this package now requires ES2020 support. If using this package in an environment that does not support ES2020 completely, consider investigating these two dependency changes and transpiling any packages using ES2020 syntax.
• Update @metamask/eth-sig-util to v5 (#180)
• Update minimum supported version of @metamask/browser-passworder from v4.0.1 to v4.0.2 (#182)
• Remove bip39 dependency (#179)

Fixed

• Fix support for asynchronous addAccounts HD Keyring method (#176)
  • This method was asynchronous, but was called synchronously. Currently the method does not do anything asynchronous so this should have no functional impact, but this ensures any future errors or asynchronous steps added to that method work correctly in the future.