Releases: MetaMask/rpc-errors
Releases · MetaMask/rpc-errors
7.0.1
Changed
- Bump
@metamask/utils
from ^9.0.0
to ^10.0.0
(#161)
7.0.0
Changed
- BREAKING: Preserve original messages during error serialization by default (#158)
- The behavior introduced in
5.0.0
of overwriting the original message is available by passing shouldPreserveMessage: false
to serializeError()
.
- BREAKING: Bump minimum Node.js version from 16 to 18 (#154)
6.4.0
Changed
- Migrate to
ts-bridge
(#152)
- Migrates to ts-bridge from
tsup
, which may resolve issues when importing this package in CommonJS or ESM.
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