2.5.0 (2024-01-25)
2.4.0 (2024-01-17)
2.3.1 (2023-12-15)
- Throw error if
useWallet
hook is being used outside theWalletProvider
(#125) (3ccc5e0) - Use named export of
zustand/shallow
to suppress deprecation warning (263a56b)
2.3.0 (2023-11-29)
2.2.0 (2023-10-11)
2.1.3 (2023-09-22)
2.1.2 (2023-09-12)
2.1.1 (2023-08-11)
2.1.0 (2023-08-07)
2.0.0 (2023-06-27)
- Add unit tests (#61)
- The function used to initialize providers in version 1.x is no longer exported by the library. Use the
useInitializeProviders
hook or manually construct the wallet providers map that gets passed to theWalletProvider
. - There is no longer a "default" provider configuration. All providers to be supported must be explicitly defined.
- Wallet provider peer dependencies (SDK/client libraries) are no longer dynamically imported behind the scenes. The modules must be statically imported and passed to the
clientStatic
property when initializing the provider.
1.3.3 (2023-06-24)
- Upgrade
@blockshake/defly-connect
to v1.1.5 (32c7bba)
1.3.2 (2023-06-21)
- Upgrade
@blockshake/defly-connect
to v1.1.3 (b25cbeb)
1.3.1 (2023-06-20)
- Handle nested transaction arrays in
signTransactions
(#79)
- Update
signTransactions
type signature inuseWallet
hook
1.3.0 (2023-04-28)
1.2.12 (2023-04-24)
- Add missing unsigned txns to group in Defly client (#69)
1.2.11 (2023-03-29)
- Fixes jest tests, initial CI pipeline, adding commitizen, starter config for automation tools (#58)
1.2.10 (2023-03-26)
- Fixes dependency resolution errors on
npm install
for local development (aea17fc)
1.2.9 (2023-03-23)
- Fix return type of
groupTransactionsBySender
in base client (07ae640)
1.2.8 (2023-03-23)
- Upgrade @perawallet/connect to v1.2.1 (496000c)
1.2.7 (2023-03-17)
- Migration to AlgoSigner v1.10.0, which adds support for rekeyed signing (fbff1ee)
- ESLint added and source files formatted following the new ESLint/Prettier config (77b8f03)
1.2.6 (2023-03-14)
- Handle varying payload lengths in WalletConnect
signTransactions
method (79a9228)
1.2.5 (2023-03-14)
- Fix handling signed transactions in WalletConnect client (c973514)
1.2.4 (2023-03-11)
- Only reconnect to active providers in
reconnectProviders
(0a48316)
1.2.3 (2023-03-06)
- Upgrade
@perawallet/connect
tov1.1.1
, which adds Ledger support for Pera Web Wallet
1.2.2 (2023-02-07)
- Upgrade
algosdk
so that polyfills forBuffer
andCrypto
globals are no longer necessary.
1.2.1 (2023-01-25)
- Support signing transaction groups from multiple accounts with Pera
- Remove deprecated functions
1.2.0 (2023-01-19)
- adding algoworld swapper to
used by
(#29) (1bca5ab) - adding new mnemonic wallet provider for e2e testing (#28) (ca38100)
1.1.6 (2023-01-16)
- Change provider initialization failure from console error to warning.
1.1.5 (2023-01-16)
- Add
status
,isReady
andisActive
properties to check status of the providers.
1.0.5 (2022-12-29)
- Add the
indexesToSign
option tosignTransactions
to optionally specify which indexes of the group should be signed. - Add the
returnGroup
parameter tosignTransactions
to specify if all transactions that were passed should be returned, or just the ones signed by the provider.
- Fix the
signer
method so that it accepts both signed and unsigned transactions.
1.0.4 (2022-12-15)
- Enable multiple WalletConnect sessions (e.g., Pera and Defly) to be active at the same time.
- Fix hydration errors that occur with SSR frameworks like Next.js.
- Prevent the providers from being initialized during SSR, as many of them rely on client side globals like
window
andAudio
.
1.0.3 (2022-12-13)
- Prevent KMD from prompting password on app mount.
- Fix a bug where default KMD configuration wasn't valid.
- Fix a bug where providers would not disconnect if the session was killed in the wallet app (affected Defly and Pera)
1.0.2 (2022-12-07)
- remove 'audio hack' for Pera (8dc3a2d)
1.0.1 (2022-12-07)
1.0.0 (2022-12-07)
- The provider clients are now passed to child components using React Context, allowing for more configuration options.
- Provider clients provide support for both dynamic and static imports, allowing
use-wallet
to be used with frameworks that don't support dynamic imports.
- To setup the
providers
, theinitializeProviders
function should be used, and passed to theWalletProviders
context provider in the application root. - The provider ID, name, and icon are now part of the
metadata
property ofproviders
. - Using environment variables to configure the clients is deprecated.