[Snyk] Security upgrade react-native from 0.20.0 to 0.69.12

[MHxGH-ServiceAccount]

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

Snyk changed the following file(s):

• examples/SampleRN20/package.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Allocation of Resources Without Limits or Throttling SNYK-JS-QS-14724253	170

---

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

---

Note

Updates the example app dependency.

• Bumps react-native in examples/SampleRN20/package.json from 0.20.0 to 0.69.12

^{Written by Cursor Bugbot for commit d9c4a17. This will update automatically on new commits. Configure here.}

[MHxGH-ServiceAccount]

⛔ Snyk checks have failed. 2 issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (2)
⛔	Open Source Security	0	2	0	0	2 issues
✅	Licenses	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[MHxGH-ServiceAccount]

This upgrade from version 0.20.0 to 0.69.12 spans over six years of development and constitutes a complete architectural overhaul of the framework. A manual upgrade is not feasible; this should be treated as a full project migration.

Key Breaking Changes:

• New Architecture: The upgrade crosses the introduction of React Native's "New Architecture," which replaces the legacy bridge with a new JavaScript Interface (JSI), a new renderer (Fabric), and a new native module system (TurboModules). This is a fundamental rewrite of the framework's core. [5, 9, 10]
• Build System & Autolinking: The react-native link command has been removed in favor of autolinking for native dependencies, requiring a complete change in how libraries are integrated. [11]
• API Removals: Numerous components and APIs have been removed, such as ViewPropTypes, which will break many older third-party libraries and require significant code refactoring. [14]

Recommendation: Do not attempt an incremental upgrade. The recommended approach is to create a new project using the latest React Native version and migrate your application's source code and dependencies into the new project structure.

Source: React Native Upgrade Guide

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

[cursor]

Start script path incompatible with upgraded React Native

The start script references node_modules/react-native/local-cli/cli.js, which existed in React Native 0.20.0 but was removed as part of the "Lean Core" initiative around version 0.60. In React Native 0.69.12, the CLI has been extracted to @react-native-community/cli and this path no longer exists. Running npm start will fail with a "module not found" error. The script needs to be updated to use npx react-native start or the modern CLI path.

Additional Locations (1)

• examples/SampleRN20/package.json#L8-L9