[Snyk] Security upgrade react-native from 0.64.1 to 0.74.0

[Kieranties]

Snyk has created this PR to fix 1 vulnerabilities in the yarn dependencies of this project.

Snyk changed the following file(s):

• package.json
• yarn.lock

Note for zero-installs users

If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Allocation of Resources Without Limits or Throttling SNYK-JS-BRACEEXPANSION-18313044	828

Breaking Change Risk

Notice: This assessment is enhanced by AI.

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Allocation of Resources Without Limits or Throttling

[Kieranties]

Upgrading from React Native 0.64.1 to 0.74.0 is a massive undertaking that spans 10 minor versions and includes fundamental architectural changes. This is a major migration project that will require significant effort and careful planning.

Key Breaking Changes and Migration Pillars:

• The New Architecture (Fabric & TurboModules): The most significant change is the rollout of the New Architecture. Support was introduced as an opt-in with version 0.68 and becomes the default for new projects in 0.74. This new architecture replaces the legacy Bridge with the JavaScript Interface (JSI), fundamentally changing how the JavaScript and Native layers communicate. Migrating will require enabling the new architecture and ensuring all native modules and UI components are compatible.

• API & Component Removals: Several long-deprecated components and APIs have been removed from the core library. You will need to migrate to community-maintained packages:

  • PropTypes: Completely removed in 0.74. Code must be migrated to use a type system like TypeScript.
  • AsyncStorage & MaskedViewIOS: Removed in 0.71.
  • Picker & PickerIOS: Removed in 0.66.
  • DatePickerAndroid: Removed in 0.67.

• Environment and Tooling Upgrades: The required development environment has changed significantly:

  • Node.js: Version 0.68 and later require at least Node.js 14.
  • Android: The minimum SDK has been raised to 23 (Android 6.0) in 0.74. The target SDK was updated to 31 in 0.68, which also enforced the use of JDK 11 and Gradle 7+.
  • TypeScript: Starting with 0.71, TypeScript is the default for new projects, and type definitions are now bundled with React Native, making the @types/react-native package obsolete.

• Layout and Styling Changes:

  • Yoga 3.0: Introduced in 0.74, this new version of the layout engine makes styling more predictable but may cause subtle changes to existing layouts.
  • Flexbox gap: Support for gap, rowGap, and columnGap was added in 0.71, which may simplify layouts but could conflict with existing margin-based workarounds.

Recommendation: Do not attempt this upgrade in a single step. Use the official React Native Upgrade Helper to generate a diff between each consecutive version (e.g., 0.64 → 0.65, 0.65 → 0.66, and so on). Address the breaking changes for each version incrementally. This will be a complex and time-consuming process that requires thorough testing at each stage.

Source: React Native Upgrade Helper, React Native Release Notes

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.