Update React version in example

[Nicolapps]

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Summary by CodeRabbit

• Chores
  • Updated React and React DOM dependencies to the latest patch version.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

Version bump for React and React DOM dependencies from 19.2.1 to 19.2.2 in the example package configuration. No new dependencies added or removed; all other package dependencies remain unchanged.

Changes

Cohort / File(s)	Summary
Dependency version updates example/package.json	Bumped React and React DOM from 19.2.1 to 19.2.2

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• Update the React version used in example #25: Modifies the same file (example/package.json) and bumps React and React DOM to the preceding version (19.2.1), establishing a direct version progression.

Poem

🐰 A patch so small, yet oh so neat,
React bumps its version suite complete,
From 19.2.1 to 19.2.2 we hop,
Dependencies fresh, improvements won't stop! ✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: updating React and React DOM versions from 19.2.1 to 19.2.2 in the example directory.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch nicolas/update-react-again

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 8eb8b02 and c81cf9e.

⛔ Files ignored due to path filters (1)

• example/package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (1)

• example/package.json (1 hunks)

🧰 Additional context used

📓 Path-based instructions (1)

example/package.json

📄 CodeRabbit inference engine (CLAUDE.md)

After making changes to component functions, run codegen with: cd example/ && npm run dev -- --once

Files:

• example/package.json

🧠 Learnings (1)

📚 Learning: 2025-12-03T20:37:39.411Z

Learnt from: CR
Repo: get-convex/expo-push-notifications PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-12-03T20:37:39.411Z
Learning: Applies to example/package.json : After making changes to component functions, run codegen with: `cd example/ && npm run dev -- --once`

Applied to files:

• example/package.json

🔇 Additional comments (2)

example/package.json (2)

35-36: Version consistency looks good.

React and React DOM versions are properly kept in sync, and @types/react at ~19.2.0 remains compatible with the new patch version.

---

35-36: React and React-dom 19.2.2 are valid published versions. The patch-level update from 19.2.1 to 19.2.2 is safe—no new security advisories reported for 19.2.2, and the critical CVE-2025-55182 (React2Shell) that affected 19.2.0 was already fixed in 19.2.1.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/get-convex/expo-push-notifications/@convex-dev/expo-push-notifications@26

commit: c81cf9e