RepoJournal
Meta Meta
104 wires and counting

$ follow Meta

Keep up with Meta in about 3 minutes: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

or

fair warning: these emails are deeply technical. diffs, version numbers, CVEs, benchmark deltas. if that's not your idea of a good read, this isn't your newsletter.

Folds into your digest — weekly by default, monthly if you prefer. Unsubscribe in one click.

$ status

wire 2026-09-01
stories 11
RSS Archive Topics

© 2026 RepoJournal Home Showcase Explore How it works Privacy

$ the-wire · showcase

React unobserve fix, Jest ESM subpath bug, RN stable API guards

By RepoJournal · Filed · About Meta

jackpope Jakub Piasecki SimenB HuzaifaChaudary Peter Abbondanzo josepharhar
6 people shipped this
jackpope @jackpope 2 cited Jakub Piasecki @j-piasecki 2 cited SimenB @SimenB 2 cited HuzaifaChaudary @HuzaifaChaudary 2 cited Peter Abbondanzo @Abbondanzo 1 cited josepharhar @josepharhar

React stops leaking detached IntersectionObserver targets, Jest's 30.5.0 ESM subpath bug gets a fix, and React Native tightens its stable API visibility.

React's DOM fix changes how fragment IntersectionObserver and ResizeObserver targets are cleaned up: targets used to stay observed after a child was removed so the exit record could fire, but that left the observer holding detached nodes; now ResizeObserver targets are unobserved immediately, and IntersectionObserver unobserve is delayed until after paint so the exit still lands [1]. If the same node is reinserted before that flush, the pending unobserve is canceled, preventing a later cleanup from detaching a still-attached child [2]. Once the exit record fires, the strong ref is dropped, so observers no longer pin detached nodes [1]. In Jest, 30.5.0 broke all ESM resolves of subpaths in the `imports` field: every subpath starts with `#`, and `splitQueryAndFragment` in `packages/jest-runtime/src/internals/EsmLoader.ts` treats the first `#` as a fragment delimiter, so `import { value } from '#dep'` fails with 'The requested module `#dep` does not provide an export named `value`'; the fix stops treating a leading `#` as a fragment delimiter so subpath imports resolve correctly [3][4]. Jest also refined its config warnings: the change only warns about global-only options where they are actually ignored, fixing cases where a project directory without its own config resolved to the root config and the comparison misfired [5][6]. React Native added an AI code review bot via `@expo/code-review-cli`, which leaves a single comment on PRs with findings from three reviewers (correctness, security, consistency) and never blocks merging or auto-approves [7]; separately, `devtoolsruntimesettings` and `jsc:JSCRuntime` are now classified under the C++ stable API three-tier visibility model, with consumers that opt into `RN_STRICT_API` getting a suppressible warning if they include `JSCRuntime.h` directly [8][9].

Action items

References

  1. [1] [DOM] Unobserve fragment IntersectionObserver targets after exit ↗ facebook/react
  2. [2] [DOM] Unobserve fragment IntersectionObserver targets after exit (#37408) ↗ facebook/react
  3. [3] fix(jest-runtime): do not treat a leading `#` as a fragment delimiter ↗ facebook/jest
  4. [4] fix(jest-runtime): do not treat a leading `#` as a fragment delimiter (#16413) ↗ facebook/jest
  5. [5] fix(jest-config): only warn about global-only options where they're actually ignored ↗ facebook/jest
  6. [6] fix(jest-config): only warn about global-only options where they're actually ignored (#16411) ↗ facebook/jest
  7. [7] Add @expo/code-review-cli (#58021) ↗ facebook/react-native
  8. [8] Cover `devtoolsruntimesettings` with Stable API guards (#58131) ↗ facebook/react-native
  9. [9] Cover `jsc:JSCRuntime` with Stable API guards (#58023) ↗ facebook/react-native

$ ls meta/reviews/ # the step-back reads

the week in review React Native sheds Paper-era internals the month in review React, React Native, and Jest harden the stack
Topics: JavaScript AI / ML Full archive →

Quick answers

What shipped in Meta on September 1, 2026?
React stops leaking detached IntersectionObserver targets, Jest's 30.5.0 ESM subpath bug gets a fix, and React Native tightens its stable API visibility. In total, 7 commits and 4 pull requests landed.
Who contributed to Meta on September 1, 2026?
6 developers shipped this update, including jackpope, josepharhar, Peter Abbondanzo, Jakub Piasecki, SimenB, and HuzaifaChaudary.
What were the notable Meta updates?
[DOM] Unobserve fragment IntersectionObserver targets after exit, [DOM] Unobserve fragment IntersectionObserver targets after exit (#37408), and fix(jest-runtime): do not treat a leading `#` as a fragment delimiter.
♥

$ log Meta --recent

React Native adds Stable API guards to renderer attributed string 1 shipped React Native fixes bridgeless ordering and commits dev-machine paths 28 shipped React Native sheds Paper-era internals, stabilizes Maestro e2e 22 shipped Jest strips TS types sans transformer; React fixes DevTools release inputs 40 shipped

$ log --all # elsewhere on the wire

FastAPI & Pydantic Pydantic fixes Mypy plugin crash, tightens datetime constraints @laravel LSP skips diagnostics for interpolated strings

$ ls showcases/

Rails Django Laravel Node.js Go Vercel Vue.js Kubernetes HashiCorp Arch Linux Linux Anthropic

$ init your-desk

RepoJournal can write one of these for any repo you care about. Sign in with GitHub, pick your repos and sources, and your desk gets a wire like this one every morning.