[Snyk] Security upgrade react-native from 0.42.3 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):

• example/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

Security dependency upgrade

• Updates react-native in example/package.json from 0.42.3 to 0.69.12 to address a reported vulnerability

No application code changes included.

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

[MHxGH-ServiceAccount]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 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 is a massive upgrade, jumping from a 2017 version to a 2022 version, and involves fundamental architectural changes that will require a significant migration effort.

Key Breaking Changes:

• New Architecture: The upgrade crosses the introduction of React Native's "New Architecture" (starting around v0.68), which replaces the legacy Bridge with a new system using Fabric for rendering and TurboModules for native modules. This is a foundational shift for performance but requires migrating all native dependencies. [1, 3, 4]
• Core Component Extraction: Many components once included in the core react-native package (e.g., WebView, AsyncStorage) have been removed. They must now be installed from separate community-maintained packages and imported into your project.
• Autolinking: The react-native link command has been removed in favor of autolinking, changing the workflow for integrating native dependencies. [5, 19]

Source: React Native Release Notes
Recommendation: This upgrade cannot be merged directly. It requires a dedicated project to incrementally upgrade the application, address breaking API changes, and migrate dependencies. Using the official React Native Upgrade Helper tool is essential. [15, 21]

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

[cursor]

React Native 0.69 requires React 18, not React 15

Upgrading react-native to 0.69.12 without updating the react dependency creates a version incompatibility. React Native 0.69.x requires React 18.x as a peer dependency, but react remains at 15.4.2. This mismatch will cause the application to fail at runtime since React Native 0.69 uses React 18 APIs that don't exist in React 15.

 

[cursor]

TypeScript types don't match upgraded React Native version

The @types/react-native package remains at version 0.42.3 while react-native was upgraded to 0.69.12. This significant mismatch means the TypeScript type definitions won't match the actual APIs available in the installed React Native version, leading to incorrect type checking and potential runtime errors from using deprecated or changed APIs.

 

[cursor]

Start script path doesn't exist in React Native 0.69

The start script references node_modules/react-native/local-cli/cli.js, which was the CLI path in React Native 0.42.x. In React Native 0.69, the CLI was extracted to @react-native-community/cli as part of the "Lean Core" initiative and this path no longer exists. Running npm start will fail with a "module not found" error after this upgrade.