upgrading-expo
Upgrade Expo SDK versions
- License 许可
- MIT
- 最近更新
- 2026-05-10
- Stars
- ★ 1
- Forks
- 1
01 前言 Front Matter
- name
- upgrading-expo
- risk
- safe
- source
- https://github.com/expo/skills/tree/main/plugins/upgrading-expo
- date_added
- 2026-02-27
- description
- Upgrade Expo SDK versions
03 SKILL.md 正文
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:
- Pre-Upgrade Planning: Review release notes and breaking changes
- Dependency Updates: Update packages for SDK compatibility
- Configuration Migration: Update app.json and configuration files
- Code Updates: Migrate deprecated APIs to new versions
- 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
# 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
# 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 installinstead ofnpm installfor Expo packages - Check package compatibility with new SDK version
- Resolve peer dependency warnings
Configuration Changes
- Update
app.jsonfor 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-doctorto verify setup
Resources
For more information, see the source repository.
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
04 同仓库更多 Skills
zustand-store-ts
Create Zustand stores following established patterns with proper TypeScript types and middleware.
zod-validation-expert
Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC.
zinc-database
Access ZINC (230M+ purchasable compounds). Search by ZINC ID/SMILES, similarity searches, 3D-ready structures for docking, analog discovery, for virtual screening and drug discovery.
zarr-python
Chunked N-D arrays for cloud storage. Compressed arrays, parallel I/O, S3/GCS integration, NumPy/Dask/Xarray compatible, for large-scale scientific computing pipelines.
zapier-workflows
Manage and trigger pre-built Zapier workflows and MCP tool orchestration. Use when user mentions workflows, Zaps, automations, daily digest, research, search, lead tracking, expenses, or asks to "run" any process. Also handles Perplexity-based research and Google Sheets data tracking.
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 - these platforms have their own patterns, pitfalls, and breaking points. This skill covers when to use which platform, how to build reliable automations, and when to graduate to code-based solutions. Key insight: Zapier optimizes for simplicity and integrations (7000+ apps), Make optimizes for power