@metamask/providers
Advanced tools
Changelog
[17.1.1]
@metamask/json-rpc-engine
to ^9.0.1
(#345)@metamask/json-rpc-middleware-stream
to ^8.0.1
(#345)@metamask/rpc-errors
to ^6.3.1
(#345)@metamask/superstruct
to ^3.1.0
(#338)@metamask/utils
to ^9.0.0
(#345)@ts-bridge/cli
to ^0.2.0
(#343)
json
file imports, where an extension was appended to the file name after compilation (e.g. *.json.cjs
or *.json.mjs
).Changelog
[17.1.0]
@metamask/json-rpc-middleware-stream
from ^7.0.1
to ^8.0.0
(#327)@metamask/json-rpc-engine
from ^8.0.2
to ^9.0.0
(#328)extension-port-stream
from ^3.0.0
to ^4.1.0
(#331)@metamask/utils
from ^8.4.0
to ^8.5.0
(#329)@metamask/rpc-errors
from ^6.2.1
to ^6.3.0
(#326)Node16
or NodeNext
as its moduleResolution
option.exports
field in package.json
linked to these files. This is an anti-pattern and was rightfully flagged by the "Are the Types Wrong?" tool as "masquerading as CJS".extension-port-stream
import to ensure compatibility with bundlers such as Vite (#331)