Skip to content
Open
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 example/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@
"jcore-react-native": "^2.3.0",
"jpush-react-native": "^3.2.1",
"react": "18.2.0",
"react-native": "0.74.1"
"react-native": "0.76.0"

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

React Native devDependencies not updated to match 0.76.0

High Severity

Upgrading react-native to 0.76.0 without updating the corresponding @react-native/babel-preset, @react-native/eslint-config, @react-native/metro-config, and @react-native/typescript-config packages from 0.74.83 to their 0.76.x counterparts creates a version mismatch. These @react-native/* scoped packages are tightly coupled to the react-native version and are likely to cause build failures or runtime errors with incompatible configurations.

Additional Locations (1)
Fix in Cursor Fix in Web

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

React version incompatible with react-native 0.76.0 peer dependency

High Severity

react-native 0.76.0 requires react 18.3.x as a peer dependency, but react remains pinned at 18.2.0. This version mismatch will cause npm peer dependency errors during installation and may lead to runtime incompatibilities, since React 18.3 includes preparatory deprecation warnings needed for the New Architecture features enabled by default in 0.76.

Fix in Cursor Fix in Web

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🔴 Incomplete react-native upgrade: @react-native/ devDependencies left at 0.74.x*

The react-native dependency was bumped from 0.74.1 to 0.76.0, but the @react-native/* devDependencies (@react-native/babel-preset, @react-native/eslint-config, @react-native/metro-config, @react-native/typescript-config) are all still pinned at 0.74.83 (example/package.json:22-25). These packages are versioned in lockstep with react-native and are expected to match the major.minor version. Using the 0.74.x tooling packages with react-native 0.76.0 will likely cause build failures or runtime errors in the example app (e.g., metro config incompatibilities, missing babel transforms for new architecture features introduced in 0.76).

Prompt for agents
In example/package.json, update the @react-native/* devDependencies on lines 22-25 to match the react-native 0.76.x version. Specifically, update:
  - @react-native/babel-preset from 0.74.83 to the 0.76.x version
  - @react-native/eslint-config from 0.74.83 to the 0.76.x version
  - @react-native/metro-config from 0.74.83 to the 0.76.x version
  - @react-native/typescript-config from 0.74.83 to the 0.76.x version

Also verify that react 18.2.0 (line 15) is compatible with react-native 0.76.0; react-native 0.76 may require a newer version of react (e.g., 18.3.1).
Open in Devin Review

Was this helpful? React with 👍 or 👎 to provide feedback.

},
"devDependencies": {
"@babel/core": "^7.20.0",
Expand Down