Releases: MetaMask/providers
Releases · MetaMask/providers
18.2.0
Added
- Add new export for
initializeInpageProvider
with legacy build system support (#391)- Previously this module could be imported from
/dist/initializeInpageProvider
, but this only worked with build systems that support theexports
field (e.g. browserify). - This new
initializeInpageProvider
export has a JavaScript redirect for older build systems, so it should work correctly in all cases.
- Previously this module could be imported from
18.1.2
18.1.1
18.1.0
18.0.0
17.2.1
17.2.0
17.1.2
17.1.1
Changed
- Bump
@metamask/json-rpc-engine
to^9.0.1
(#345) - Bump
@metamask/json-rpc-middleware-stream
to^8.0.1
(#345) - Bump
@metamask/rpc-errors
to^6.3.1
(#345) - Bump
@metamask/superstruct
to^3.1.0
(#338) - Bump
@metamask/utils
to^9.0.0
(#345)
Fixed
- Bump devDependency
@ts-bridge/cli
to^0.2.0
(#343)- Fixes incorrect handling of
json
file imports, where an extension was appended to the file name after compilation (e.g.*.json.cjs
or*.json.mjs
).
- Fixes incorrect handling of
17.1.0
Changed
- Bump
@metamask/json-rpc-middleware-stream
from^7.0.1
to^8.0.0
(#327) - Bump
@metamask/json-rpc-engine
from^8.0.2
to^9.0.0
(#328) - Bump
extension-port-stream
from^3.0.0
to^4.1.0
(#331) - Bump
@metamask/utils
from^8.4.0
to^8.5.0
(#329) - Bump
@metamask/rpc-errors
from^6.2.1
to^6.3.0
(#326)
Fixed
- Produce and export ESM-compatible TypeScript type declaration files in addition to CommonJS-compatible declaration files (#336)
- This fixes the issue of this package being unusable by any TypeScript project that uses
Node16
orNodeNext
as itsmoduleResolution
option. - 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".
- This fixes the issue of this package being unusable by any TypeScript project that uses
- Remove chunk files (#336).
- 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.
- Use named
extension-port-stream
import to ensure compatibility with bundlers such as Vite (#331)