Best use case
upgrading-expo is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Upgrade Expo SDK versions
Teams using upgrading-expo should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/upgrading-expo/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How upgrading-expo Compares
| Feature / Agent | upgrading-expo | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Upgrade Expo SDK versions
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Upgrading Expo ## Overview Upgrade Expo SDK versions safely, handling breaking changes, dependencies, and configuration updates. ## When to Use This Skill Use this skill when you need to upgrade Expo SDK versions. Use this skill when: - Upgrading to a new Expo SDK version - Handling breaking changes between SDK versions - Updating dependencies for compatibility - Migrating deprecated APIs to new versions - Preparing apps for new Expo features ## Instructions This skill guides you through upgrading Expo SDK versions: 1. **Pre-Upgrade Planning**: Review release notes and breaking changes 2. **Dependency Updates**: Update packages for SDK compatibility 3. **Configuration Migration**: Update app.json and configuration files 4. **Code Updates**: Migrate deprecated APIs to new versions 5. **Testing**: Verify app functionality after upgrade ## Upgrade Process ### 1. Pre-Upgrade Checklist - Review Expo SDK release notes - Identify breaking changes affecting your app - Check compatibility of third-party packages - Backup current project state - Create a feature branch for the upgrade ### 2. Update Expo SDK ```bash # Update Expo CLI npm install -g expo-cli@latest # Upgrade Expo SDK npx expo install expo@latest # Update all Expo packages npx expo install --fix ``` ### 3. Handle Breaking Changes - Review migration guides for breaking changes - Update deprecated API calls - Modify configuration files as needed - Update native dependencies if required - Test affected features thoroughly ### 4. Update Dependencies ```bash # Check for outdated packages npx expo-doctor # Update packages to compatible versions npx expo install --fix # Verify compatibility npx expo-doctor ``` ### 5. Testing - Test core app functionality - Verify native modules work correctly - Check for runtime errors - Test on both iOS and Android - Verify app store builds still work ## Common Issues ### Dependency Conflicts - Use `expo install` instead of `npm install` for Expo packages - Check package compatibility with new SDK version - Resolve peer dependency warnings ### Configuration Changes - Update `app.json` for new SDK requirements - Migrate deprecated configuration options - Update native configuration files if needed ### Breaking API Changes - Review API migration guides - Update code to use new APIs - Test affected features after changes ## Best Practices - Always upgrade in a feature branch - Test thoroughly before merging - Review release notes carefully - Update dependencies incrementally - Keep Expo CLI updated - Use `expo-doctor` to verify setup ## Resources For more information, see the [source repository](https://github.com/expo/skills/tree/main/plugins/upgrading-expo).
Related Skills
expo-deployment
Deploy Expo apps to production
azure-monitor-opentelemetry-exporter-py
Azure Monitor OpenTelemetry Exporter for Python. Use for low-level OpenTelemetry export to Application Insights.
azure-monitor-opentelemetry-exporter-java
Azure Monitor OpenTelemetry Exporter for Java. Export OpenTelemetry traces, metrics, and logs to Azure Monitor/Application Insights.
zustand-store-ts
Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state/action separation. Use when building React state management, creating global stores, or implementing reacti...
zoom-automation
Automate Zoom meeting creation, management, recordings, webinars, and participant tracking via Rube MCP (Composio). Always search tools first for current schemas.
zoho-crm-automation
Automate Zoho CRM tasks via Rube MCP (Composio): create/update records, search contacts, manage leads, and convert leads. Always search tools first for current schemas.
zendesk-automation
Automate Zendesk tasks via Rube MCP (Composio): tickets, users, organizations, replies. Always search tools first for current schemas.
zapier-make-patterns
No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity ...
youtube-summarizer
Extract transcripts from YouTube videos and generate comprehensive, detailed summaries using intelligent analysis frameworks
youtube-automation
Automate YouTube tasks via Rube MCP (Composio): upload videos, manage playlists, search content, get analytics, and handle comments. Always search tools first for current schemas.
xss-html-injection
This skill should be used when the user asks to "test for XSS vulnerabilities", "perform cross-site scripting attacks", "identify HTML injection flaws", "exploit client-side injection...
xlsx-official
Comprehensive spreadsheet creation, editing, and analysis with support for formulas, formatting, data analysis, and visualization. When Claude needs to work with spreadsheets (.xlsx, .xlsm, .csv, ....