@wagmi/connectors 4.1.1 → 4.1.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1,2 +1,2 @@
1
- export const version = '4.1.1';
1
+ export const version = '4.1.2';
2
2
  //# sourceMappingURL=version.js.map
@@ -1,2 +1,2 @@
1
- export declare const version = "4.1.1";
1
+ export declare const version = "4.1.2";
2
2
  //# sourceMappingURL=version.d.ts.map
@@ -6,7 +6,7 @@ export type WalletConnectParameters = Evaluate<{
6
6
  /**
7
7
  * If a new chain is added to a previously existing configured connector `chains`, this flag
8
8
  * will determine if that chain should be considered as stale. A stale chain is a chain that
9
- * WalletConnect has yet to establish a relationship with (ie. the user has not approved or
9
+ * WalletConnect has yet to establish a relationship with (e.g. the user has not approved or
10
10
  * rejected the chain).
11
11
  *
12
12
  * Preface: Whereas WalletConnect v1 supported dynamic chain switching, WalletConnect v2 requires
@@ -21,7 +21,7 @@ export type WalletConnectParameters = Evaluate<{
21
21
  * session, the connector will disconnect upon the dapp auto-connecting, and the user will have to
22
22
  * reconnect to the dapp (revalidate the chain) in order to approve the newly added chain.
23
23
  * This is the default behavior to avoid an unexpected error upon switching chains which may
24
- * be a confusing user experience (ie. the user will not know they have to reconnect
24
+ * be a confusing user experience (e.g. the user will not know they have to reconnect
25
25
  * unless the dapp handles these types of errors).
26
26
  *
27
27
  * If `false`, the new chain will be treated as a validated chain. This means that if the user
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "@wagmi/connectors",
3
3
  "description": "Collection of connectors for Wagmi",
4
- "version": "4.1.1",
4
+ "version": "4.1.2",
5
5
  "license": "MIT",
6
6
  "repository": {
7
7
  "type": "git",
@@ -30,7 +30,7 @@
30
30
  "peerDependencies": {
31
31
  "typescript": ">=5.0.4",
32
32
  "viem": "2.x",
33
- "@wagmi/core": "2.1.1"
33
+ "@wagmi/core": "2.1.2"
34
34
  },
35
35
  "peerDependenciesMeta": {
36
36
  "typescript": {
package/src/version.ts CHANGED
@@ -1 +1 @@
1
- export const version = '4.1.1'
1
+ export const version = '4.1.2'
@@ -23,7 +23,7 @@ export type WalletConnectParameters = Evaluate<
23
23
  /**
24
24
  * If a new chain is added to a previously existing configured connector `chains`, this flag
25
25
  * will determine if that chain should be considered as stale. A stale chain is a chain that
26
- * WalletConnect has yet to establish a relationship with (ie. the user has not approved or
26
+ * WalletConnect has yet to establish a relationship with (e.g. the user has not approved or
27
27
  * rejected the chain).
28
28
  *
29
29
  * Preface: Whereas WalletConnect v1 supported dynamic chain switching, WalletConnect v2 requires
@@ -38,7 +38,7 @@ export type WalletConnectParameters = Evaluate<
38
38
  * session, the connector will disconnect upon the dapp auto-connecting, and the user will have to
39
39
  * reconnect to the dapp (revalidate the chain) in order to approve the newly added chain.
40
40
  * This is the default behavior to avoid an unexpected error upon switching chains which may
41
- * be a confusing user experience (ie. the user will not know they have to reconnect
41
+ * be a confusing user experience (e.g. the user will not know they have to reconnect
42
42
  * unless the dapp handles these types of errors).
43
43
  *
44
44
  * If `false`, the new chain will be treated as a validated chain. This means that if the user