hashgraph / hedera-metamask-snaps

Metamask snaps offer the ability to create npm package that can be used to enhance the wallet capabilities for chains and DApps.
Apache License 2.0
3 stars 2 forks source link

chore(deps): Bump @metamask/providers from 16.1.0 to 17.1.0 in /packages/hedera-wallet-snap/packages/snap #464

Closed dependabot[bot] closed 1 week ago

dependabot[bot] commented 3 weeks ago

Bumps @metamask/providers from 16.1.0 to 17.1.0.

Release notes

Sourced from @​metamask/providers's releases.

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

17.0.0

Changed

  • Change provider RPC error log severity from error to warn (#323)

Fixed

  • BREAKING: Change webextension-polyfill from dependency to peerDependency (#319)
    • Users are now expected to have the polyfill in their environment
Changelog

Sourced from @​metamask/providers's changelog.

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

[17.0.0]

Changed

  • Change provider RPC error log severity from error to warn (#323)

Fixed

  • BREAKING: Change webextension-polyfill from dependency to peerDependency (#319)
    • Users are now expected to have the polyfill in their environment
Commits
  • 9d88271 17.1.0 (#337)
  • 0b26cd1 Replace tsup with ts-bridge as build tool (#336)
  • c749bea Bump @​metamask/json-rpc-middleware-stream from 7.0.1 to 8.0.0 (#327)
  • 725929f Bump @​metamask/json-rpc-engine from 8.0.2 to 9.0.0 (#328)
  • 878a6bb refactor: Use named extension-port-stream import for Vite compatibility (#331)
  • 4afb435 Bump @​metamask/utils from 8.4.0 to 8.5.0 (#329)
  • 2169c02 Bump @​metamask/rpc-errors from 6.2.1 to 6.3.0 (#326)
  • d9be2b5 Bump ws from 8.13.0 to 8.17.1 in the npm_and_yarn group across 1 directory (#...
  • 0575d8e Bump braces from 3.0.2 to 3.0.3 in the npm_and_yarn group across 1 directory ...
  • c1965db chore(devdeps): @​lavamoat/allow-scripts@^3.0.0->^3.0.4 (#322)
  • Additional commits viewable in compare view


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
dependabot[bot] commented 1 week ago

Looks like @metamask/providers is up-to-date now, so this is no longer needed.