AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

upgrading-react-native

Upgrades React Native apps to newer versions by applying rn-diff-purge template diffs, updating package.json dependencies, migrating native iOS and Android configuration, resolving CocoaPods and Gradle changes, and handling breaking API updates. Use when upgrading React Native, bumping RN version, updating from RN 0.x to 0.y, or migrating Expo SDK alongside a React Native upgrade.

Original source
callstackincubator
License
MIT
Pinned revision
59e9d17446a248b21d86f078fcd0bd2d36db1ca4

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read callstackincubator--upgrading-react-native at revision 59e9d17446a248b21d86f078fcd0bd2d36db1ca4, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 8

references/upgrading-dependencies.md


title: Upgrading Dependencies impact: HIGH tags: react-native, dependencies, compatibility, migration

Skill: Upgrading Dependencies

Common dependency issues and mitigations when upgrading React Native.

Quick Checks

npm ls --depth=0

Dependency Risk and Migration Plan

  1. Review compatibility signals:
  2. If react is upgraded, run react.md for companion package alignment and React 19 rules.
  3. Handle known risky packages:
    • react-native-fast-image -> prefer @d11/react-native-fast-image or expo-image (confirm with user)
    • @react-native-cookies/cookies -> prefer @preeternal/react-native-cookie-manager (confirm with user)
    • react-native-code-push -> treat as incompatible; disable for upgrade and consider @appzung/react-native-code-push, @bravemobile/react-native-code-push, or expo-updates
    • react-native-image-crop-picker -> upgrade to >=0.51.1; if unstable, plan migration to expo-image-picker (confirm with user)
    • react-native-network-logger - lists react and react-native in peer deps as * which can be misleading. Upgrade to v2 if target_version >= 0.79.
    • react-native-permissions - upgrade to v5 if possible (requires RN 0.74+)
  4. Apply additional cleanup rules:
    • If @rnx-kit/metro-resolver-symlinks is present, remove it from deps and metro.config.js (Metro supports symlinks since 0.72)
    • If app uses react-native-localize timezone APIs and @callstack/timezone-hermes-fix is missing, ask whether to add it
  5. If no safe alternative is found for a critical dependency, ask for explicit user confirmation before continuing.
  6. Read only breaking/manual steps from RN blog posts between current_version and target_version.

Related Skills