Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion package.json
Original file line number Diff line number Diff line change
Expand Up @@ -41,7 +41,7 @@
"@growthbook/growthbook": "^1.2.0",
"@react-native-async-storage/async-storage": "1.23.1",
"@react-native-community/masked-view": "^0.1.11",
"@react-native/metro-config": "^0.75.0-main",
"@react-native/metro-config": "^0.80.1",

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

critical

Upgrading @react-native/metro-config from a pre-release version (^0.75.0-main) to ^0.80.1 is a significant change, especially within an Expo project. This upgrade pulls in a new major version of metro-config which may introduce breaking changes to the build process.

In an Expo-managed project, it is highly recommended to manage toolchain versions by upgrading the expo package itself, rather than individual packages like this. This ensures all related dependencies are kept at compatible versions, preventing potential build failures or runtime errors.

"@react-navigation/compat": "^5.3.15",
"@react-navigation/native": "^6.1.17",
"@react-navigation/stack": "^6.3.29",
Expand Down
Loading
Loading