skills.rest
raphaelmans
raphaelmansCOMMUNITY
Explore all skills by this author →
GitHub

upgrading-expo

Guide Expo SDK upgrades and resolve dependency migration issues.

Updated Feb 28, 2026
Search Tags:#sdk#diagnostics#upgrade#react-native#breaking-changes#expo#prebuild
One-click install
npx skills add https://github.com/raphaelmans/agent-skills --skill upgrading-expo-raphaelmans
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: upgrading-expo
Source: https://github.com/raphaelmans/agent-skills/tree/main/upgrading-expo
Command: npx skills add https://github.com/raphaelmans/agent-skills --skill upgrading-expo-raphaelmans

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Guides teams through upgrading Expo SDK versions and resolving dependency issues that arise during migrations.

Core Features & Use Cases

  • Step-by-step upgrade process including diagnostics, prebuilds, cache cleanup, and config migrations.
  • Guidance for handling breaking changes across Expo SDK versions and migrating dependencies.
  • Real-world scenario: upgrading from one SDK version to another while keeping native builds functional.

Quick Start

Follow the upgrade playbook to upgrade Expo SDKs and resolve dependency issues in your project.

Frequently Asked Questions about upgrading-expo

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I upgrade my Expo SDK version without breaking my React Native app?▼

To upgrade Expo SDK versions safely, follow a structured workflow that includes running diagnostics, handling prebuilds, clearing caches, and migrating deprecated packages. This process addresses breaking changes and keeps native builds functional.

What are breaking changes in Expo SDK and how do I handle them during an upgrade?▼

Breaking changes during an Expo SDK upgrade involve deprecated packages and configuration shifts that stop existing code from working. You resolve them by following a guided migration process that identifies dependency issues and updates config files.

When do I need to run prebuilds in a React Native Expo migration?▼

You need to run prebuilds during an Expo SDK migration when upgrading across major versions to regenerate native project files. This step is essential for resolving dependency issues and ensuring native builds remain functional after config migrations.

Does this Expo upgrade workflow support resolving dependency issues across major SDK versions?▼

Yes, the upgrade workflow supports React Native Expo apps undergoing major SDK version migrations. It provides diagnostics and guidance for resolving dependency issues, handling deprecated packages, and migrating configurations across major version jumps.

Why does my Expo build fail after an SDK upgrade and how do I fix it?▼

Expo builds fail after an SDK upgrade due to unresolved breaking changes and outdated dependencies. You fix them by following an upgrade playbook that includes clearing the cache, running diagnostics, executing prebuilds, and migrating deprecated packages.

What is the best way to migrate deprecated packages when upgrading Expo SDK?▼

The best way to migrate deprecated packages is to follow a comprehensive upgrade workflow that includes running diagnostics and config migrations. This ensures dependency issues are resolved systematically while keeping native builds functional across major versions.

Related Skills

Explore More Software Engineering Skills→
emilyLi2020emilyLi2020
2

upgrading-expo

Upgrades Expo SDK versions in React Native apps with step-by-step guidance and validation.

Community
Advanced
rex009xrex009x

upgrading-expo

Generate migration plans for upgrading Expo SDK versions and deprecated native modules.

Community
Advanced
mjamoremjamore

upgrading-expo

Upgrade Expo SDK versions and fix dependency and native compatibility issues.

Community
Intermediate
skillcreatoraiskillcreatorai
1.1k

upgrading-expo

Upgrade Expo SDK versions and resolve dependency conflicts across React Native projects.

Community
Advanced