upgrading-expo

Upgrade Expo SDK versions and fix dependency issues in projects.

Updated Jan 28, 2026
One-click install
npx skills add https://github.com/apostolos-geyer/StoliStack --skill upgrading-expo-apostolos-geyer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: upgrading-expo
Source: https://github.com/apostolos-geyer/StoliStack/tree/main/.agents/skills/upgrading-expo
Command: npx skills add https://github.com/apostolos-geyer/StoliStack --skill upgrading-expo-apostolos-geyer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Upgrading Expo SDK versions and aligning dependencies can be error-prone and time-consuming due to breaking changes, native config drift, and prebuild requirements.

Core Features & Use Cases

  • Guided upgrade path: Step-by-step instructions to upgrade Expo SDK versions, verify dependencies, and perform prebuild cleanups.
  • Dependency hygiene: Checks for deprecated packages, breaking changes, and migration notes to keep projects healthy.
  • Use Case: A team upgrading from Expo SDK 52 to 54 with React Native changes can follow this guide to update packages, adjust app.json, run prebuild, and validate builds.

Quick Start

Upgrade Expo to the target SDK, run diagnostics, and perform a prebuild to validate the migration.

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 and fix dependency issues?

To upgrade your Expo SDK version and fix dependency issues, follow a guided protocol that checks for deprecated packages, applies breaking changes, updates app configuration, and runs prebuild steps to validate the migration.

What are the breaking changes I need to check when migrating Expo SDK versions?

When migrating Expo SDK versions, you need to check for breaking changes by reviewing migration notes, identifying deprecated packages, and verifying native configuration updates to ensure production-grade compatibility.

What is the best way to handle prebuild steps during an Expo SDK upgrade?

The best way to handle prebuild steps during an Expo SDK upgrade is to perform prebuild cleanups that validate your native config drift and ensure the build succeeds after updating dependencies.

Does this Expo upgrade protocol support jumping across multiple SDK versions?

Yes, this upgrade protocol supports upgrading Expo SDKs across multiple versions by running diagnostics, applying breaking changes checks, and validating builds to ensure a safe migration path.

Why do I need to run diagnostics when upgrading my Expo project dependencies?

You need to run diagnostics when upgrading Expo project dependencies to identify deprecated packages, detect configuration drift, and resolve breaking changes before performing the prebuild.

Can I use this guide to adjust app.json and run prebuild for an Expo migration?

Yes, you can use this guide to adjust app.json, update necessary packages, run prebuild cleanups, and validate builds as part of a complete Expo SDK migration workflow.