114 wires and counting
$ status: archived — this briefing has stopped; the archive stays readable. browse live briefings →

$ status

wire 2026-08-16
stories 2

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

JEST FIXES ES MODULE RESOLVER LOADING

By RepoJournal · Filed · About Meta · Composed from the cited sources · methodology

Jest can now load custom resolvers written as ES modules, closing a gap that forced developers back to CommonJS workarounds.

The jest-resolve module shipped a fix [1] that extends loadResolver to accept ES module exports alongside the existing function and object hook patterns. Previously, importing a resolver written as an ES module would fail validation even if it exported a valid sync or async hook [2]. The change maintains backward compatibility: loadResolver still accepts functions or objects with sync/async properties, but now correctly handles the module format that modern Node.js favors. This solves issue #16284 and closes PR #16332 with a single commit across the repo this period.

Quick answers

What shipped in Meta on August 16, 2026?
Jest can now load custom resolvers written as ES modules, closing a gap that forced developers back to CommonJS workarounds. In total, 1 commits and 1 pull requests landed.
Who contributed to Meta on August 16, 2026?
1 developer shipped this update, including MahinAnowar.
What were the notable Meta updates?
fix(jest-resolve): load a user resolver written as an ES module and fix(jest-resolve): load a user resolver written as an ES module (#16332).