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
The Exponential Puck Framework
No description provided.
markdown-exporter
Markdown exporter for transform Markdown text to DOCX, PPTX, XLSX, PDF, PNG, HTML, MD, CSV, JSON, JSONL, XML, Mermaid files, and extract code blocks in Markdown to Python, Bash,JS and etc files. Also known as the md_exporter skill.
expo-framework-rule
Expo Framework-specific guidelines. Includes best practices for Views, Blueprints, and Extensions.
abaqus-export
Export Abaqus geometry and results. Use when user mentions exporting to STL, STEP, CSV, or generating input files for external use.
chatgpt-exporter-ultimate
Export ALL your ChatGPT conversations instantly — no 24h wait, no extensions. Works via browser relay OR standalone bookmarklet. Extracts full message history with timestamps, roles, and metadata. One command, one JSON file, done.
database-query-and-export
Query SQLite, PostgreSQL, and MySQL databases and export results to CSV/JSON. Use when: (1) Extracting data for reports, (2) Database backup and migration, (3) Data analysis workflows, or (4) Automated database queries.
analyze-chat-export
Export and analyze VS Code Copilot chat logs for retrospective metrics. Extracts model usage, tool invocations, approval patterns, and timing data.
agent-exporter
Upload tailored resume to cloud or attach to user session. Handles final formatting and delivery.
bgo
Automates the complete Blender build-go workflow, from building and packaging your extension/add-on to removing old versions, installing, enabling, and launching Blender for quick testing and iteration.
vercel-deploy
Deploy applications and websites to Vercel. Use this skill when the user requests deployment actions such as "Deploy my app", "Deploy this to production", "Create a preview deployment", "Deploy and give me the link", or "Push this live". No authentication required - returns preview URL and claimable deployment link.
vercel-deploy-claimable
Deploy applications and websites to Vercel. Use this skill when the user requests deployment actions such as 'Deploy my app', 'Deploy this to production', 'Create a preview deployment', 'Deploy and...
vercel-composition-patterns
React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.