AGENT SKILL

upgrading-expo

Upgrade Expo SDK versions

License 许可
MIT
最近更新
2026-11-10
Stars
★ 1
Forks
0

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:

  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

# 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 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.

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

YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

vercel-sandbox

Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include "Vercel Sandbox browser", "microVM Chrome", "agent-browser in sandbox", "browser automation on Vercel", or any task requiring Chrome in a Vercel Sandbox.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

slack

Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include "check my Slack", "what channels have unreads", "send a message to", "search Slack for", "extract from Slack", "find who said", or any task requiring programmatic Slack interaction.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

electron

Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include "automate Slack app", "control VS Code", "interact with Discord app", "test this Electron app", "connect to desktop app", or any task requiring automation of a native Electron application.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

dogfood

Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

shadcn

Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", "switch to --preset", and for building a design system or applying a DESIGN.md or brand spec to shadcn/ui.

★ 1