Skip to content

Releases: MetaMask/providers

18.2.0

27 Nov 20:42
157d24f
Compare
Choose a tag to compare

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 the exports field (e.g. browserify).
    • This new initializeInpageProvider export has a JavaScript redirect for older build systems, so it should work correctly in all cases.

18.1.2

27 Nov 20:00
8464e2b
Compare
Choose a tag to compare

Fixed

  • Allow optional jsonRpcStreamName for initializeInpageProvider (#390)
    • This parameter was accidentally made required in v18.1.0

18.1.1

29 Oct 11:55
047ea9b
Compare
Choose a tag to compare

Changed

18.1.0

18 Oct 11:06
2c43cf7
Compare
Choose a tag to compare

Added

  • Add intializeInpageProvider as package export (#380)

Fixed

  • Remove spurious typescript reference (#381)

18.0.0

17 Oct 00:14
64d6649
Compare
Choose a tag to compare

Changed

  • BREAKING: Bump @metamask/json-rpc-engine from ^9.0.1 to ^10.0.0 (#378)
  • BREAKING: Bump @metamask/rpc-errors from ^6.4.0 to ^7.0.0 (#373)
  • Bump @metamask/object-multiplex from ^2.0.0 to ^2.1.0 (#375)
  • Bump @metamask/utils from ^9.2.1 to ^9.3.0 (#370)

17.2.1

03 Oct 09:01
6b5f099
Compare
Choose a tag to compare

Fixed

  • Add support for edge-chromium to createExternalExtensionProvider (#318, #368)
  • Fix ESM-related build issues (#362, #363)

17.2.0

09 Sep 15:49
d3283aa
Compare
Choose a tag to compare

Changed

  • Bump @metamask/utils from 9.1.0 to 9.2.1 (#357)
  • Bump micromatch from 4.0.5 to 4.0.8 in the npm_and_yarn group (#359)

Removed

  • Remove deprecation console warnings when accessing window.ethereum.chainId, window.ethereum.networkVersion, and window.ethereum.selectedAddress (#360)

17.1.2

23 Jul 12:57
1f215b6
Compare
Choose a tag to compare

Added

  • Add @metamask/providers/stream-provider export (#351)
    • This replaces the @metamask/providers/dist/StreamProvider export. It still exists for backwards compatibility, but will be removed in a future major release.

Changed

  • Bump @metamask/utils from 9.0.0 to 9.1.0 (#348)

17.1.1

12 Jul 18:18
9068123
Compare
Choose a tag to compare

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).

17.1.0

27 Jun 17:03
9d88271
Compare
Choose a tag to compare

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 or NodeNext as its moduleResolution option.
    • Previously, this package shipped with only one variant of type declaration files, and these files were only CommonJS-compatible, and the 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".
  • 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)