Skip to content

revert: Revert moving connect-multichain into peerDep for ecosystem packages#323

Open
jiexi wants to merge 3 commits into
mainfrom
jl/revert-buildtime-versioning
Open

revert: Revert moving connect-multichain into peerDep for ecosystem packages#323
jiexi wants to merge 3 commits into
mainfrom
jl/revert-buildtime-versioning

Conversation

@jiexi

@jiexi jiexi commented Jun 10, 2026

Copy link
Copy Markdown
Member

Explanation

Reverts just the peerDep changes from 7786de8 . The devex degradation for library consumers having to install two peerDeps (ecosystem client, and multichain client) isn't worth the gains from build time warnings.

References

Fixes: https://consensys.slack.com/archives/C058P09HT17/p1781040721508819?thread_ts=1781037006.244619&cid=C058P09HT17

Checklist

  • I've updated the test suite for new or updated code as appropriate
  • I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
  • I've communicated my changes to consumers by updating changelogs for packages I've changed, highlighting breaking changes as necessary
  • I've prepared draft pull requests for clients and consumer packages to resolve any breaking changes

@jiexi jiexi requested a review from a team as a code owner June 10, 2026 17:00

### Changed

- `@metamask/connect-multichain` is no longer a peer dependency and will be installed transitively as a regular dependency ([#323](https://github.com/MetaMask/connect-monorepo/pull/323))

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Trying to reason about whether this is breaking again or not 🤔

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Its not.

@adonesky1 adonesky1 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants