Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
“React Native is listening” refers to changes in React Native 0.72, announced June 21, 2023, after the team gathered developer feedback. The most prominent updates centered on Metro: beta support for symlinks and package.json exports, alongside a revised Metro configuration setup. These are release-era details, not current upgrade instructions; React Native 0.72 is an older release.
Why React Native 0.72 was described as listening
The phrase comes from Bytes issue 198, published June 22, 2023. Its release story focused on the React Native team responding to feedback gathered through its 2022 community survey, especially requests for improvements to Metro, React Native’s JavaScript build tool. The official 0.72 announcement also highlighted better error handling and developer-experience improvements, but the Metro changes are the clearest examples of feedback shaping the release.
The team described symlink support as one of Metro’s most-requested features. In the 0.72 announcement, the authors wrote: “Symlink support continues to be one of the top-requested features in Metro and, in React Native 0.72, we are happy to announce beta support for it.” Read the React Native 0.72 announcement.
Free tools Windows power users keep installed
One-click scans. No signup required.
What changed in Metro in React Native 0.72?
Beta symlink support for monorepos and pnpm
A symlink points from one filesystem location to another. Development setups that share packages across a monorepo, or use pnpm’s package layout, can depend on symlinks. Without Metro support, those layouts could require workarounds for the bundler to find and process linked code.
#1 Best Overall
React Native 0.72 added beta support intended to make these workflows easier. The release-era opt-in was resolver.unstable_enableSymlinks. The setting name and beta status matter: this describes how the feature was introduced in 0.72, not advice to copy that configuration into a project using a later React Native version.
Beta support for package.json exports
React Native 0.72 also introduced beta support for the exports field in package.json, enabled at the time with resolver.unstable_enablePackageExports. A package can use exports to define its public entry points, subpath aliases, and conditional targets—for example, different files for React Native or browser environments.
Rank #2
This changes how Metro resolves imports. When a package has an exports field, Metro consults it before other package fields. As a result, an import that previously resolved through another path may stop working if it is not listed in exports. The feature can therefore affect edge cases and should not be treated as a resolution-neutral switch. The official explanation describes the behavior and its implications in more detail: React Native’s package exports explainer.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
What changed in metro.config.js?
React Native 0.72 changed how the CLI loads Metro configuration. The revised setup moved responsibility for extending the base React Native Metro configuration into each project’s metro.config.js. The 0.72 announcement warned developers that the new format would become required in 0.73, so the change was also a migration heads-up.
Rank #3
React Native 0.73 removed the fallback copy of the default configuration, making the updated format required. The 0.73 announcement also said that symlink support had become stable and was enabled by default. See the React Native 0.73 announcement for those later release changes. Symlink support still had monorepo edge cases; stable and default did not mean every layout worked without adjustment.
How did the changes progress after 0.72?
| Change | React Native 0.72 | React Native 0.73 |
|---|---|---|
| Metro symlink support | Beta; opt in with resolver.unstable_enableSymlinks. |
Stable and enabled by default, with some monorepo edge cases remaining. |
| Metro configuration format | Updated setup introduced; the announcement said it would be required in 0.73. | Required after the fallback copy of defaults was removed. |
Package.json exports |
Beta; opt in with resolver.unstable_enablePackageExports. |
The 0.73 announcement cited here does not establish a later status for this feature. |
What this release story does—and does not—establish
React Native 0.72 is a historical release, and the official React Native blog listing includes a 0.87 release entry. The 0.72 announcement is useful for understanding the origin and intent of the Metro work, but it is not enough to determine the right configuration or migration steps for a current project. Those depend on the React Native version and project setup in use.
Rank #4
The release coverage documents requested capabilities and their status; it does not provide an independently useful statistic measuring their adoption or performance impact. It supports the conclusion that the team prioritized developer feedback, not a numerical claim about how many projects benefited.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
