Releases: TxnLab/use-wallet
Releases · TxnLab/use-wallet
1.1.6
How to upgrade
Yarn
npm install @txnlab/use-wallet@latest
NPM
yarn upgrade @txnlab/use-wallet --latest
What's Changed
- Change provider initialization failure from console error to warning
1.1.5
How to upgrade
Yarn
npm install @txnlab/use-wallet@latest
NPM
yarn upgrade @txnlab/use-wallet --latest
What's Changed
- chore: update README
- feat: add status, isReady and isActive properties to check status of the providers
- chore: update package.json
Full Changelog: v1.0.5...v1.1.5
1.0.5
How to upgrade
Yarn
npm install @txnlab/use-wallet@latest
NPM
yarn upgrade @txnlab/use-wallet --latest
What's Changed
- Fix the
signer
method so that it accepts both signed and unsigned transactions. - 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.
Full Changelog: v1.0.4...v1.0.5
1.0.4
How to upgrade
Yarn
npm install @txnlab/use-wallet@latest
NPM
yarn upgrade @txnlab/use-wallet --latest
⚠️ Important! To enable multiple WalletConnect sessions, upgrade the following peer dependencies.
Yarn
npm install @blockshake/defly-connect@latest
NPM
yarn upgrade @blockshake/defly-connect --latest
What's Changed
- Fix hydration errors that occur with SSR frameworks like Next.js
- Prevent the providers from being initialized during SSR, since many of them rely on client side globals like
window
andAudio
. - Enable multiple WalletConnect sessions (e.g., Pera and Defly) to be active at the same time.
Full Changelog: v1.0.3...v1.0.4
1.0.3
- 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).
Full Changelog: v1.0.2...v1.0.3
1.0.2
What's Changed
- Remove audio workaround from Pera client. On iOS, going into background mode breaks WalletConnect's websocket connection. To get around this,
use-wallet
plays an audio file in the background which persists the connection. This hack is now a part of Pera Connect's library, so this workaround is no longer needed.
Full Changelog: v1.0.1...v1.0.2
1.0.1
What's Changed
- Update peer dependencies
- Update README
1.0.0
What's Changed
- The provider clients are now passed to child components using React Context, allowing for more configuration options.
- Using environment variables to configure the clients has been deprecated.
- Provider clients provide support for both dynamic and static imports, allowing
use-wallet
to be used with frameworks that don't support dynamic imports. See Provider Configuration for details.
Breaking Changes
- To setup the
providers
, theinitializeProviders
function should be used, and passed to theWalletProviders
context provider in the application root. See the Set up the Wallet Provider section for details on how to setupuse-wallet
. - The provider ID, name, and icon are now part of the
metadata
property ofproviders
. See Connect for details on how to setup the connect buttons for the providers. - Using environment variables to configure the clients is deprecated. See Provider Configuration for details on how to configure the clients.
0.1.23
What's Changed
- Dynamically import wallet provider dependencies and reduce bundle size by @gabrielkuettel in #9
- Use first and last valid rounds to determine how many rounds to wait to confirm transactions by @gabrielkuettel in #13
- Handle signing transactions for multiple connected accounts by @gabrielkuettel in #14
- Upgrade to Zustand v4 by @gabrielkuettel in #11
Full Changelog: https://github.com/TxnLab/use-wallet/commits/v0.1.23