[Snyk] Security upgrade react-native from 0.42.3 to 0.69.12#26
[Snyk] Security upgrade react-native from 0.42.3 to 0.69.12#26MHxGH-ServiceAccount wants to merge 1 commit intomasterfrom
Conversation
The following vulnerabilities are fixed with an upgrade: - https://snyk.io/vuln/SNYK-JS-QS-14724253
⛔ Snyk checks have failed. 4 issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
|
This is a massive upgrade across dozens of major versions, representing a fundamental architectural overhaul rather than a simple update. Migrating from version 0.42.3 will require a complete project refactor. Key Breaking Changes:
Source: React Native Release Notes
|
| "dependencies": { | ||
| "react": "15.4.2", | ||
| "react-native": "0.42.3", | ||
| "react-native": "0.69.12", |
There was a problem hiding this comment.
React version incompatible with upgraded react-native
The react-native upgrade from 0.42.3 to 0.69.12 creates a version incompatibility. React Native 0.69 requires React 18.x, but react remains at version 15.4.2. This mismatch will cause the application to fail at runtime since React Native 0.69 relies on React 18 features and APIs that don't exist in React 15.
| "dependencies": { | ||
| "react": "15.4.2", | ||
| "react-native": "0.42.3", | ||
| "react-native": "0.69.12", |
There was a problem hiding this comment.
Start script path no longer exists in react-native
The start script references node_modules/react-native/local-cli/cli.js, but this path doesn't exist in react-native 0.69.12. The CLI was moved to cli.js at the package root and later extracted to @react-native-community/cli. The start command will fail with a "module not found" error.
| "dependencies": { | ||
| "react": "15.4.2", | ||
| "react-native": "0.42.3", | ||
| "react-native": "0.69.12", |
There was a problem hiding this comment.
Postinstall uses deprecated react-native link command
The postinstall script uses react-native link, which was deprecated in React Native 0.60 when autolinking was introduced. In React Native 0.69, this command either fails or behaves unexpectedly, preventing proper native module linking during installation.
| "dependencies": { | ||
| "react": "15.4.2", | ||
| "react-native": "0.42.3", | ||
| "react-native": "0.69.12", |
There was a problem hiding this comment.
Deprecated babel preset incompatible with react-native 0.69
The babel-preset-react-native package at version 1.9.1 was deprecated and replaced by metro-react-native-babel-preset starting from React Native 0.57. With react-native 0.69.12, this outdated preset will fail to properly transform the JavaScript code, causing build failures when bundling the application.
| "dependencies": { | ||
| "react": "15.4.2", | ||
| "react-native": "0.42.3", | ||
| "react-native": "0.69.12", |
There was a problem hiding this comment.
react-test-renderer version mismatches required React version
The react-test-renderer at version 15.4.2 must match the React version being used. Since react-native 0.69.12 requires React 18.x, but react-test-renderer remains at 15.4.2, tests will fail due to version mismatch errors between the renderer and React internals.
Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.
Snyk changed the following file(s):
examples/SampleRN42/package.jsonVulnerabilities that will be fixed with an upgrade:
SNYK-JS-QS-14724253
Important
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 dependency in the example app.
react-nativefrom0.42.3to0.69.12inexamples/SampleRN42/package.jsonWritten by Cursor Bugbot for commit 22cf8e5. This will update automatically on new commits. Configure here.