deps: @metamask/rpc-errors@^6.3.1->^7.0.0

[legobeat]

• Update @metamask/rpc-errors from ^6.3.1 to ^7.0.0
• Set shouldPreserveMessage to false for all invocations of serializeError
  • Ref: feat: Preserve original messages during error serialization by default rpc-errors#158

---

Open question

Currently snaps-rpc-methods tests fail because some errors now have the new (old) behavior of not wrapping error messages.

Haven't figured out if there is something else at play as well/instead but looks like at least @metamask/json-rpc-engine calls serializeError with default arguments which are not currently overridable (though that dependency is still on v6 so TBD)

If the above is correct, which of these options are preferred?

1. Add/rewrite middleware in snaps to handle this
2. Add constructor option to JsonRpcEngine to allow overriding serializeError options
3. Rewrite tests in snaps-rpc-methods to accomodate to new defaults

---

Related

• deps: @metamask/rpc-errors@^6.3.1->^7.0.0 eth-json-rpc-middleware#342
• deps(json-rpc-engine): @metamask/rpc-errors@^6.3.1->^7.0.0 core#4773
• deps: @metamask/rpc-errors@^6.3.1->^7.0.0 core#4769
• deps: @metamask/rpc-errors@^6.3.1->^7.0.0 providers#369

[socket-security]

New dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@metamask/[email protected]	None	0	171 kB	metamaskbot

View full report↗︎