build!: build packages with ts-bridge

[Mrtenz]

This updates all packages to build with ts-bridge instead of tsc. This has the benefit that packages will be built as CJS modules and ESM modules at the same time.

I've also modernised eth-hd-keyring in this process, as it was previously a single JS file. For now it's running TypeScript with allowJs, but this file can be properly converted to TypeScript in the future.

Breaking changes

• Each package now has an exports field, meaning subpath imports (import '@metamask/eth-hd-keyring/dist/foo';) are no longer possible, unless explicitly stated in the exports field.

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@ts-bridge/[email protected]	None	0	192 kB	mrten
npm/@ts-bridge/[email protected]	filesystem, unsafe	0	72.9 kB	mrten
npm/[email protected]	None	0	146 kB	guybedford

🚮 Removed packages: npm/[email protected]

View full report↗︎

[legobeat]

Might want to couple this with an upgrade of typescript to min 5.5: ts-bridge/ts-bridge#67 (comment)

[ccharly]

@metamaskbot publish-previews

[github-actions]

Preview builds have been published. See these instructions (from the core monorepo) for more information about preview builds.

Expand for full list of packages and versions.

{
  "@metamask-previews/keyring-api": "10.1.0-3416820",
  "@metamask-previews/eth-hd-keyring": "7.0.4-3416820",
  "@metamask-previews/eth-ledger-bridge-keyring": "6.0.0-3416820",
  "@metamask-previews/eth-simple-keyring": "6.0.5-3416820",
  "@metamask-previews/eth-trezor-keyring": "4.0.0-3416820",
  "@metamask-previews/eth-snap-keyring": "5.0.1-3416820"
}

[ccharly]

I was able to run the E2E tests on the extension side using a bunch of previews builds, everything looks fine.

Some tests are failing, but I truly think this is not related to that PR, but more about the latest changes we made on the mainline (the extension + the core repo are not up-to-date with our latest release).

Here's the PRs I used for tests:

• chore: use resolutions to test ts-bridge with some accounts packages metamask-extension#28455
• chore: use resolutions to test ts-bridge with some accounts packages core#4932

Here's the CI report:

• The dedupe fail being a non-issue here
• The 2 failing tests might be because of latest changes, but not related to the move to ts-bridge