@metamask-previews/network-controller 26.0.0-preview-d6fe4594 → 26.0.0-preview-bc80feb8
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.
- package/CHANGELOG.md +0 -16
- package/dist/NetworkController.cjs +0 -4
- package/dist/NetworkController.cjs.map +1 -1
- package/dist/NetworkController.d.cts +12 -135
- package/dist/NetworkController.d.cts.map +1 -1
- package/dist/NetworkController.d.mts +12 -135
- package/dist/NetworkController.d.mts.map +1 -1
- package/dist/NetworkController.mjs +0 -4
- package/dist/NetworkController.mjs.map +1 -1
- package/dist/create-auto-managed-network-client.cjs +1 -4
- package/dist/create-auto-managed-network-client.cjs.map +1 -1
- package/dist/create-auto-managed-network-client.d.cts +2 -5
- package/dist/create-auto-managed-network-client.d.cts.map +1 -1
- package/dist/create-auto-managed-network-client.d.mts +2 -5
- package/dist/create-auto-managed-network-client.d.mts.map +1 -1
- package/dist/create-auto-managed-network-client.mjs +1 -4
- package/dist/create-auto-managed-network-client.mjs.map +1 -1
- package/dist/create-network-client.cjs +42 -132
- package/dist/create-network-client.cjs.map +1 -1
- package/dist/create-network-client.d.cts +2 -5
- package/dist/create-network-client.d.cts.map +1 -1
- package/dist/create-network-client.d.mts +2 -5
- package/dist/create-network-client.d.mts.map +1 -1
- package/dist/create-network-client.mjs +42 -132
- package/dist/create-network-client.mjs.map +1 -1
- package/dist/index.cjs.map +1 -1
- package/dist/index.d.cts +1 -1
- package/dist/index.d.cts.map +1 -1
- package/dist/index.d.mts +1 -1
- package/dist/index.d.mts.map +1 -1
- package/dist/index.mjs.map +1 -1
- package/dist/rpc-service/rpc-service-chain.cjs +39 -247
- package/dist/rpc-service/rpc-service-chain.cjs.map +1 -1
- package/dist/rpc-service/rpc-service-chain.d.cts +25 -106
- package/dist/rpc-service/rpc-service-chain.d.cts.map +1 -1
- package/dist/rpc-service/rpc-service-chain.d.mts +25 -106
- package/dist/rpc-service/rpc-service-chain.d.mts.map +1 -1
- package/dist/rpc-service/rpc-service-chain.mjs +39 -247
- package/dist/rpc-service/rpc-service-chain.mjs.map +1 -1
- package/dist/rpc-service/rpc-service-requestable.cjs.map +1 -1
- package/dist/rpc-service/rpc-service-requestable.d.cts +5 -15
- package/dist/rpc-service/rpc-service-requestable.d.cts.map +1 -1
- package/dist/rpc-service/rpc-service-requestable.d.mts +5 -15
- package/dist/rpc-service/rpc-service-requestable.d.mts.map +1 -1
- package/dist/rpc-service/rpc-service-requestable.mjs.map +1 -1
- package/dist/rpc-service/rpc-service.cjs +33 -65
- package/dist/rpc-service/rpc-service.cjs.map +1 -1
- package/dist/rpc-service/rpc-service.d.cts +24 -33
- package/dist/rpc-service/rpc-service.d.cts.map +1 -1
- package/dist/rpc-service/rpc-service.d.mts +24 -33
- package/dist/rpc-service/rpc-service.d.mts.map +1 -1
- package/dist/rpc-service/rpc-service.mjs +34 -66
- package/dist/rpc-service/rpc-service.mjs.map +1 -1
- package/dist/rpc-service/shared.cjs.map +1 -1
- package/dist/rpc-service/shared.d.cts +3 -25
- package/dist/rpc-service/shared.d.cts.map +1 -1
- package/dist/rpc-service/shared.d.mts +3 -25
- package/dist/rpc-service/shared.d.mts.map +1 -1
- package/dist/rpc-service/shared.mjs.map +1 -1
- package/package.json +1 -2
package/CHANGELOG.md
CHANGED
|
@@ -7,24 +7,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
|
|
|
7
7
|
|
|
8
8
|
## [Unreleased]
|
|
9
9
|
|
|
10
|
-
### Added
|
|
11
|
-
|
|
12
|
-
- Add `NetworkController:rpcEndpointChainAvailable` messenger event ([#7166](https://github.com/MetaMask/core/pull/7166))
|
|
13
|
-
- This is a counterpart to the (new) `NetworkController:rpcEndpointChainUnavailable` and `NetworkController:rpcEndpointChainDegraded` events, but is published when a successful request to an endpoint within a chain of endpoints is made either initially or following a previously established degraded or unavailable status.
|
|
14
|
-
|
|
15
10
|
### Changed
|
|
16
11
|
|
|
17
|
-
- **BREAKING:** Split up and update payload data for `NetworkController:rpcEndpointDegraded` and `NetworkController:rpcEndpointUnavailable` ([#7166](https://github.com/MetaMask/core/pull/7166))
|
|
18
|
-
- `NetworkController:rpcEndpointDegraded` and `NetworkController:rpcEndpointUnavailable` still exist and retain the same behavior as before.
|
|
19
|
-
- New events are `NetworkController:rpcEndpointChainDegraded` and `NetworkController:rpcEndpointChainUnavailable`, and are designed to represent an entire chain of endpoints. They are also guaranteed to not be published multiple times in a row. In particular, `NetworkController:rpcEndpointChainUnavailable` is published only after trying all of the endpoints for a chain and when the underlying circuit for the last endpoint breaks, not as each primary's or failover's circuit breaks.
|
|
20
|
-
- The event payloads have been changed:
|
|
21
|
-
- For individual endpoint events (`NetworkController:rpcEndpointUnavailable`, `NetworkController:rpcEndpointDegraded`): `failoverEndpointUrl` has been removed, and `primaryEndpointUrl` has been added. In addition, `networkClientId` has been added to the payload.
|
|
22
|
-
- For chain-level events (`NetworkController:rpcEndpointChainUnavailable`, `NetworkController:rpcEndpointChainDegraded`, `NetworkController:rpcEndpointChainAvailable`): These include `chainId`, `networkClientId`, and event-specific fields (e.g., `error`, `endpointUrl`) but do not include `primaryEndpointUrl`. Consumers can derive endpoint information from the `networkClientId` using `NetworkController:getNetworkClientById` or `NetworkController:getNetworkConfigurationByNetworkClientId`.
|
|
23
|
-
- **BREAKING:** Rename and update payload data for `NetworkController:rpcEndpointRequestRetried` ([#7166](https://github.com/MetaMask/core/pull/7166))
|
|
24
|
-
- This event is now called `NetworkController:rpcEndpointRetried`.
|
|
25
|
-
- The event payload has been changed as well: `failoverEndpointUrl` has been removed, and `primaryEndpointUrl` has been added. In addition, `networkClientId` and `attempt` have been added to the payload.
|
|
26
|
-
- **BREAKING:** Update `AbstractRpcService`/`RpcServiceRequestable` to remove `{ isolated: true }` from the `onBreak` event data type ([#7166](https://github.com/MetaMask/core/pull/7166))
|
|
27
|
-
- This represented the error produced when `isolate` is called on a Cockatiel circuit breaker policy. This never happens for our service (we use `isolate` internally, but this error is suppressed and cannot trigger `onBreak`)
|
|
28
12
|
- Move peer dependencies for controller and service packages to direct dependencies ([#7209](https://github.com/MetaMask/core/pull/7209))
|
|
29
13
|
- The dependencies moved are:
|
|
30
14
|
- `@metamask/error-reporting-service` (^3.0.0)
|
|
@@ -1399,7 +1399,6 @@ async function _NetworkController_determineEIP1559Compatibility(networkClientId)
|
|
|
1399
1399
|
for (const addedRpcEndpoint of addedRpcEndpoints) {
|
|
1400
1400
|
if (addedRpcEndpoint.type === RpcEndpointType.Infura) {
|
|
1401
1401
|
autoManagedNetworkClientRegistry[types_1.NetworkClientType.Infura][addedRpcEndpoint.networkClientId] = (0, create_auto_managed_network_client_1.createAutoManagedNetworkClient)({
|
|
1402
|
-
networkClientId: addedRpcEndpoint.networkClientId,
|
|
1403
1402
|
networkClientConfiguration: {
|
|
1404
1403
|
type: types_1.NetworkClientType.Infura,
|
|
1405
1404
|
chainId: networkFields.chainId,
|
|
@@ -1417,7 +1416,6 @@ async function _NetworkController_determineEIP1559Compatibility(networkClientId)
|
|
|
1417
1416
|
}
|
|
1418
1417
|
else {
|
|
1419
1418
|
autoManagedNetworkClientRegistry[types_1.NetworkClientType.Custom][addedRpcEndpoint.networkClientId] = (0, create_auto_managed_network_client_1.createAutoManagedNetworkClient)({
|
|
1420
|
-
networkClientId: addedRpcEndpoint.networkClientId,
|
|
1421
1419
|
networkClientConfiguration: {
|
|
1422
1420
|
type: types_1.NetworkClientType.Custom,
|
|
1423
1421
|
chainId: networkFields.chainId,
|
|
@@ -1477,7 +1475,6 @@ async function _NetworkController_determineEIP1559Compatibility(networkClientId)
|
|
|
1477
1475
|
return [
|
|
1478
1476
|
rpcEndpoint.networkClientId,
|
|
1479
1477
|
(0, create_auto_managed_network_client_1.createAutoManagedNetworkClient)({
|
|
1480
|
-
networkClientId: rpcEndpoint.networkClientId,
|
|
1481
1478
|
networkClientConfiguration: {
|
|
1482
1479
|
type: types_1.NetworkClientType.Infura,
|
|
1483
1480
|
network: infuraNetworkName,
|
|
@@ -1497,7 +1494,6 @@ async function _NetworkController_determineEIP1559Compatibility(networkClientId)
|
|
|
1497
1494
|
return [
|
|
1498
1495
|
rpcEndpoint.networkClientId,
|
|
1499
1496
|
(0, create_auto_managed_network_client_1.createAutoManagedNetworkClient)({
|
|
1500
|
-
networkClientId: rpcEndpoint.networkClientId,
|
|
1501
1497
|
networkClientConfiguration: {
|
|
1502
1498
|
type: types_1.NetworkClientType.Custom,
|
|
1503
1499
|
chainId: networkConfiguration.chainId,
|