Commits on Oct 27, 2023

1. Update Metro to ^0.80.0 - don't pin to exact version (facebook#41219) …

   Summary:
   
   Bump to the latest Metro release. This includes minor breaking changes to Metro subpackages that should *not* be visible to RN users.
   
   Metro release notes: https://github.com/facebook/metro/releases/tag/v0.80.0
   
   ## Moving to unpinned versioning
   Metro is a multi-package project, and not pinning to an exact version means multiple versions of `metro*` packages may appear in an RN project.
   
   This isn't unusual in the NPM ecosystem and *shouldn't* be a problem, but historically has caused issues (eg facebook#34714, facebook/metro#1017). The root cause of all of these issues, as far as we know, was fixed in facebook/metro@6d46078, a bug where Node hierarchical resolution was effectively sidestepped via a relative worker path, resulting in a mismatch between transformer and host process.
   
   In addition, the fact that `react-refresh`, `metro-react-native-babel-transformer` and `metro-react-native-babel-preset` are now fully moved into the `react-native/` scope and versioned with React Native means there are no circular dependencies between React Native and Metro, explicit or implicit, and we're much more clearly decoupled.
   
   So, we're moving to caret versioning to allow React Native users to pick up Metro fixes and features without requiring React Native releases and user upgrades.
   
   Changelog:
   [General][Changed] - Update Metro to ^v0.80.0, stop pinning to an exact version
   
   Reviewed By: GijsWeterings
   
   Differential Revision: D50731999

   

   robhogan authored and facebook-github-bot committed Oct 27, 2023
   Configuration menu

   • View commit details
   • Copy full SHA for 99f54be
   • Browse repository at this point

   Copy the full SHA

   99f54be View commit details

   Browse the repository at this point in the history