expo-upgrade
Skill2 starsChanged 20 days agoApache-2.0View on GitHub
Guidelines for upgrading Expo SDK versions and fixing dependency issues
- Deletes or force-pushes
4 other projects use a version of this, 4 of them edited.
Adopted by
Most recently taken up by
- NoyaraAI/Noyaraedited, first seen Nov 15, 2026
- deonmenezes/mobile-app-skilledited, first seen Nov 1, 2026
- mahik504/orchestra-workflowedited, first seen Oct 15, 2026
- patinaproject/skillsedited, first seen Oct 15, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 4
- deonmenezes/mobile-app-skill★ 496% same
- mahik504/orchestra-workflow★ 194% same
- NoyaraAI/Noyara★ 187% same
- patinaproject/skills★ 196% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository29 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- site/llms.txtllms.txt
- cavemanSkill
- eas-app-storesSkill
- eas-hostingSkill
- eas-observeSkill
- eas-simulatorSkill
- eas-update-insightsSkill
- eas-updateSkill
- eas-workflowsSkill
- expo-animationSkill
- expo-app-clipSkill
- expo-brownfieldSkill
- expo-data-fetchingSkill
- expo-design-systemSkill
- expo-dev-clientSkill
- expo-domSkill
- expo-examplesSkill
- expo-moduleSkill
- expo-native-uiSkill
- expo-overviewSkill
- expo-project-structureSkill
- expo-routerSkill
- expo-uiSkill
- expo-web-to-nativeSkill
- frontend-designSkill
- ios-designSkill
- ui-ux-pro-maxSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
22 rules. 11 are common, 0 are distinctive, and 11 are very specific to this project.
11
Common
Most of the 4 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
11
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 22
Check if latest is beta: https://exp.host/--/api/v2/versions (look for -preview in expoVersion)
- Common: line 51
Check for removed APIs in release notes
- Common: line 52
Update import paths for moved modules
- Common: line 54
Test all camera, audio, and video features
- Common: line 55
Verify navigation still works correctly
- Common: line 61
If upgrading requires native changes:
- Very specific: line 80
Update versioned docs links in agent instruction files (AGENTS.md).
- Common: line 81
If using Expo SDK 54 or later, ensure react-native-worklets is installed — this is required for react-native-reanimated to work.
- Very specific: line 83
Delete sdkVersion from app.json to let Expo manage it automatically
- Very specific: line 85
Keep expo-constants as a direct dependency whenever expo-router is installed.
- Very specific: line 86
After removing any dependency, immediately run npx expo-doctor and restore anything it reports as a missing required peer.
- Very specific: line 87
If the babel.config.js only contains 'babel-preset-expo', delete the file
- Very specific: line 88
If the metro.config.js only contains expo defaults, delete the file
- Common: line 101
When migrating deprecated packages, update all code usage before removing the old package.
- Very specific: line 105
Check if package.json has excluded packages:
- Very specific: line 117
Check if there are any outdated patches in the patches/ directory.
- Very specific: line 122
Use postcss.config.mjs in SDK +53.
- Common: line 126
Remove redundant metro config options:
- Common: line 138
Do not guide users to opt in to or out of Hermes V1.
- Common: line 145
If you encounter errors, misleading or outdated information in this skill, report it so Expo can improve:
- Common: line 149
Only submit when you have something specific and actionable to report.
- Very specific: line 150
If an agent repeatedly fails at an Expo task or the user has to step in, submit a brief report of the task, expected result, and what went …
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
References
- ./references/react-19.md -- SDK +54: React 19 changes (useContext → use, Context.Provider → Context, forwardRef removal)
- ./references/new-architecture.md -- SDK +53: New Architecture migration guide
- ./references/react-compiler.md -- SDK +54: React Compiler setup and migration guide
- ./references/native-tabs.md -- SDK +55: Native tabs changes (Icon/Label/Badge now accessed via NativeTabs.Trigger.*)
- ./references/expo-av-to-audio.md -- SDK +55: Migrate audio playback and recording from expo-av to expo-audio
- ./references/expo-av-to-video.md -- SDK +55: Migrate video playback from expo-av to expo-video
- ./references/react-navigation-to-expo-router.md -- SDK +56: Migrate
@react-navigation/*imports toexpo-routerentry points (codemod + manual mapping)
Beta/Preview Releases
Beta versions use .preview suffix (e.g., 55.0.0-preview.2), published under @next tag.
Check if latest is beta: https://exp.host/--/api/v2/versions (look for -preview in expoVersion)
npx expo install expo@next --fix # install betaStep-by-Step Upgrade Process
If upgrading from SDK 55 or earlier, skip SDK 56 and upgrade directly to SDK 57. Don't use
expo@57.0.8or below. SDK 55 with Hermes V1 enabled, SDK 56, and older SDK 57 releases contain a Hermes V1 memory regression that can drastically increase memory usage when usingreact-native-workletsorreact-native-reanimated.
- Upgrade Expo and dependencies
npx expo install expo@latest
npx expo install --fix- Run diagnostics:
npx expo-doctor - Clear caches and reinstall
npx expo export -p ios --clear
rm -rf node_modules .expo
watchman watch-del-allBreaking Changes Checklist
- Check for removed APIs in release notes
- Update import paths for moved modules
- Review native module changes requiring prebuild
- Test all camera, audio, and video features
- Verify navigation still works correctly
Prebuild for Native Changes
First check if ios/ and android/ directories exist in the project. If neither directory exists, the project uses Continuous Native Generation (CNG) and native projects are regenerated at build time — skip this section and "Clear caches for bare workflow" entirely.
If upgrading requires native changes:
npx expo prebuild --cleanThis regenerates the ios and android directories. Ensure the project is not a bare workflow app before running this command.
Clear caches for bare workflow
These steps only apply when ios/ and/or android/ directories exist in the project:
- Clear the cocoapods cache for iOS:
cd ios && pod install --repo-update - Clear derived data for Xcode:
npx expo run:ios --no-build-cache - Clear the Gradle cache for Android:
cd android && ./gradlew clean
Housekeeping
- Review release notes for the target SDK version at https://expo.dev/changelog
- Update versioned docs links in agent instruction files (
AGENTS.md). The default template links tohttps://docs.expo.dev/versions/v<version>/. Search fordocs.expo.dev/versions/and bump each link to the new SDK version. - If using Expo SDK 54 or later, ensure react-native-worklets is installed — this is required for react-native-reanimated to work.
- Enable React Compiler in SDK 54+ by adding
"experiments": { "reactCompiler": true }to app.json — it's stable and recommended - Delete sdkVersion from
app.jsonto let Expo manage it automatically - Review formerly implicit packages such as
@babel/core,babel-preset-expo, andexpo-constantsindividually instead of removing them wholesale. Keep any package that an installed dependency declares as a required peer. - Keep
expo-constantsas a direct dependency wheneverexpo-routeris installed. Expo Router imports it and declares it as a required peer; relying on a transitive copy can break native autolinking outside Expo Go. - After removing any dependency, immediately run
npx expo-doctorand restore anything it reports as a missing required peer. - If the babel.config.js only contains 'babel-preset-expo', delete the file
- If the metro.config.js only contains expo defaults, delete the file
Deprecated Packages
| Old Package | Replacement |
expo-av | expo-audio and expo-video |
expo-permissions | Individual package permission APIs |
@expo/vector-icons | expo-symbols (for SF Symbols) |
AsyncStorage | expo-sqlite/localStorage/install |
expo-app-loading | expo-splash-screen |
| expo-linear-gradient | experimental_backgroundImage + CSS gradients in View |
When migrating deprecated packages, update all code usage before removing the old package. For expo-av, consult the migration references to convert Audio.Sound to useAudioPlayer, Audio.Recording to useAudioRecorder, and Video components to VideoView with useVideoPlayer.
expo.install.exclude
Check if package.json has excluded packages:
{
"expo": { "install": { "exclude": ["react-native-reanimated"] } }
}Exclusions are often workarounds that may no longer be needed after upgrading. Review each one.
Removing patches
Check if there are any outdated patches in the patches/ directory. Remove them if they are no longer needed.
Postcss
autoprefixerisn't needed in SDK +53. Remove it from dependencies and checkpostcss.config.jsorpostcss.config.mjsto remove it from the plugins list.- Use
postcss.config.mjsin SDK +53.
Metro
Remove redundant metro config options:
- resolver.unstable_enablePackageExports is enabled by default in SDK +53.
experimentalImportSupportis enabled by default in SDK +54.EXPO_USE_FAST_RESOLVER=1is removed in SDK +54.- cjs and mjs extensions are supported by default in SDK +50.
- Expo webpack is deprecated, migrate to Expo Router and Metro web.
Hermes engine v1
Hermes V1 is the default on SDK 56 and later. SDK 55 apps using Hermes V1, all SDK 56 apps, and SDK 57 apps before expo@57.0.9 may encounter a memory regression when importing react-native-worklets or react-native-reanimated. Upgrade directly to SDK 57 and expo@57.0.9 or later. Do not recommend Worklets Bundle Mode as a production workaround; it is unsupported and experimental and may not work as expected.
Do not guide users to opt in to or out of Hermes V1. Changing the Hermes version from the SDK default is unsupported and has significant build and dependency-management caveats.
New Architecture
The new architecture is enabled by default, the app.json field "newArchEnabled": true is no longer needed as it's the default. Expo Go only supports the new architecture as of SDK +53.
Submitting Feedback
If you encounter errors, misleading or outdated information in this skill, report it so Expo can improve:
npx --yes @expo/agent-cli@latest feedback --category skills --subject "expo-upgrade" "<actionable feedback>"Only submit when you have something specific and actionable to report. Include as much relevant context as possible.
If an agent repeatedly fails at an Expo task or the user has to step in, submit a brief report of the task, expected result, and what went wrong using --category evals and the relevant Expo package or command as --subject.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

