All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
- Bump
@metamask/json-rpc-engine
from^10.0.1
to^10.0.2
(#5082) - Bump
@metamask/utils
from^10.0.0
to^11.0.1
(#5080)
- Bump
@metamask/utils
from^9.1.0
to^10.0.0
(#4831)
- Bump
@metamask/json-rpc-engine
to^10.0.0
(#4798)
- Produce and export ESM-compatible TypeScript type declaration files in addition to CommonJS-compatible declaration files (#4648)
- Previously, this package shipped with only one variant of type declaration
files, and these files were only CommonJS-compatible, and the
exports
field inpackage.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". All of the ATTW checks now pass.
- Previously, this package shipped with only one variant of type declaration
files, and these files were only CommonJS-compatible, and the
- Remove chunk files (#4648).
- Previously, the build tool we used to generate JavaScript files extracted common code to "chunk" files. While this was intended to make this package more tree-shakeable, it also made debugging more difficult for our development teams. These chunk files are no longer present.
- Bump TypeScript version to
~5.0.4
and setmoduleResolution
option toNode16
(#3645) - Bump
@metamask/utils
from^9.0.0
to^9.1.0
(#4529)
- Bump
@metamask/json-rpc-engine
to^9.0.1
(#4517) - Bump
@metamask/rpc-errors
to^6.3.1
(#4516) - Bump
@metamask/utils
to^9.0.0
(#4516)
- Fix incorrect notification detection logic (#4427)
- Previously, response objects with a falsy
id
property were detected as notifications. Now, we check for the absence of theid
property.
- Previously, response objects with a falsy
- BREAKING: Bump minimum Node version to 18.18 (#3611)
- Bump
@metamask/json-rpc-engine
to^9.0.0
(#4352)
- Bump
@metamask/json-rpc-engine
to^8.0.2
(#4234)
- Fix
types
field inpackage.json
(#4047)
- BREAKING: Add ESM build (#3998)
- It's no longer possible to import files from
./dist
directly.
- It's no longer possible to import files from
- Bump
@metamask/json-rpc-engine
to^8.0.0
(#4039)
- Bump
@metamask/json-rpc-engine
to^7.3.1
(#3695)
- Migrate
@metamask/json-rpc-engine
into the core monorepo (#1762)
- BREAKING: Rename package from
json-rpc-middleware-stream
to@metamask/json-rpc-middleware-stream
(#1762) - Bump
@metamask/json-rpc-engine
from^7.1.0
to^7.2.0
(#1762) - Bump
@metamask/utils
from^8.1.0
to^8.2.0
(#1762)
- Upgrade typescript version to 4.8.4 (#68)
- BREAKING: Increase minimum Node.js version to 16 (#59)
- BREAKING: Update
readable-stream
from^2.3.3
to^3.6.2
(#55) - BREAKING: Switch from legacy
json-rpc-engine
@^6.1.0
to@metamask/json-rpc-engine
@^7.1.1
(#54) - Add dependency
@metamask/utils
(#54)
- Moved json-rpc-engine from devDependencies to dependencies (#56)
- Bump @metamask/safe-event-emitter from 2.0.0 to 3.0.0 (#44)
- Fix race condition in
createStreamMiddleware
(#47)- Previously this middleware would fail to process synchronous responses on initialized streams
- Add early return in createStreamMiddleware.processsResponse method if JSON RPC request is not found (#35)
- Change error throw when response is seen for unknown request into warning displayed in console (#32)
- Added retry limit of 3 to requests (#30)
4.0.0 - 2022-10-03
- BREAKING: Add Node 12 as minimum required version #15
- Retry pending requests when notification to reconnect is received (#27)
- Add
@lavamoat/allow-scripts
to make dependency install scripts opt-in (#25)
3.0.0 - 2020-12-08
- TypeScript typings (#11)