Releases: MetaMask/rpc-errors
Releases · MetaMask/rpc-errors
6.3.1
Changed
- Bump
@metamask/utils
from ^8.3.0
to ^9.0.0
(#147)
6.3.0
Added
- Expose error causes as
cause
property (#140)
JsonRpcError
objects already had a .data.cause
property. It is now exposed as .cause
in order to to be recognized as ES Causes.
6.2.1
Fixed
- Export
OptionalDataWithOptionalCause
type (#135)
6.2.0
Added
Changed
- Update
@metamask/utils
from ^8.1.0
to ^8.3.0
(#133)
6.1.0
Changed
- Update dependency
@metamask/utils
from ^8.0.0
to ^8.1.0
(#108)
Fixed
- Exclude
dist/__fixtures__
files from published package (#114)
6.0.0
Changed
- Make Data type-parameter optional in JsonRpcError (#102)
Fixed
- BREAKING:
undefined
is now not recognized as valid JSON value
- Update dependency
@metamask/utils
from ^5.0.0
to ^8.0.0
(#101)
5.1.1
Fixed
- Allow passing unknown values as cause (#91)
- Prevously, only
Error
instances were allowed, but any value can be thrown as error
5.1.0
Added
- Allow passing a cause to predefined error functions (#83)
- This allows passing an
Error
instance as cause, by using { data: { cause: /* some error */ } }
- The error will be properly serialised when calling
serialize
5.0.0
Changed
- BREAKING: Bump minimum version to Node 16 (#68)
- BREAKING: Rewrite error serialization (#61)
- Allows errors that conform to the
JsonRpcError
type
- If errors don't conform to the type, the error will be wrapped in an internal error and the original error will be available as
data.cause
- BREAKING: Rename exports to be more generic (#75)
- JSON-RPC errors and Ethereum EIP-1474 errors are namespaced under "rpcErrors"
- Ethereum EIP-1193 Provider errors are namespaced under "providerErrors"
- BREAKING: Target
ES2020
(#77)
- Rename package to
@metamask/rpc-errors
(#67)
4.0.3
Fixed
- Correctly type
ethErrors
getter function argument objects as optional (#36)