◉RORK LABJP
●MCP — Rork now lets you add and manage your own MCP servers inside Plugins (11/21)●2.5 ROUTE — From 12/1, apps calling gemini-2.5-flash are routed to 3.5 Flash-Lite and billed at its rates (9 days left)●CHANNEL — Users report Android notification channel reads and writes failing in Expo Go●NEW — New: three clues to check before replying to a stuck-on-splash review●EXPORT — Export your projects before you downgrade or cancel a plan●SONNET 4.5 — Apps that call Sonnet 4.5 through the API should switch before it retires on 11/30●MCP — Rork now lets you add and manage your own MCP servers inside Plugins (11/21)●2.5 ROUTE — From 12/1, apps calling gemini-2.5-flash are routed to 3.5 Flash-Lite and billed at its rates (9 days left)●CHANNEL — Users report Android notification channel reads and writes failing in Expo Go●NEW — New: three clues to check before replying to a stuck-on-splash review●EXPORT — Export your projects before you downgrade or cancel a plan●SONNET 4.5 — Apps that call Sonnet 4.5 through the API should switch before it retires on 11/30
Articles/Dev Tools
⬡ Dev Tools/2026-08-17Advanced

When an Expo UI drop-in swap actually removes a dependency

Expo UI went stable in SDK 56 with drop-in replacements for eight community packages. Swapping one import does not always shrink your dependency list. Here is how to decide which swaps actually pay off, straight from the dependency graph.

Expo237React Native243Expo UIIndie Dev40Dependencies4

✦ Premium Article

I expected to delete one line from package.json. The line stayed.

Expo UI became stable in SDK 56. The pickers, sliders, and sheets that used to come from community packages are now backed by real SwiftUI and Jetpack Compose views, and eight of those packages ship drop-in replacements. The official wording is that most migrations are a one-line import swap.

The wallpaper app I run has a screen that pages through images horizontally. Because it handles both paging and jump-to-page, seeing react-native-pager-view on the replacement list felt like an easy win: swap the import, drop the dependency.

The dependency did not drop. The reason lived somewhere else entirely — in another package that requires it. And it was declared under peerDependencies, which means staring at package.json would never have shown it to me.

Before deciding whether to migrate, I needed a mechanical answer to a smaller question: does anything actually get removed?

The replacement table is not a removal table

These are the eight pairs that shipped in SDK 56. The mapping itself is public and stable. The last column is the platform support listed in the official docs as of November 2026, where the recommended @expo/ui version is ~58.0.28.

Community packageDrop-in replacementSupported (per docs)
@react-native-community/datetimepicker@expo/ui/community/datetime-pickerAndroid / iOS / Expo Go
@react-native-community/slider@expo/ui/community/sliderAndroid / iOS / Web / Expo Go
react-native-pager-view@expo/ui/community/pager-viewAndroid / iOS
@react-native-picker/picker@expo/ui/community/pickerAndroid / iOS / Web / Expo Go
@react-native-segmented-control/segmented-control@expo/ui/community/segmented-controlAndroid / iOS / Web / Expo Go
@react-native-masked-view/masked-view@expo/ui/community/masked-viewAndroid / iOS
@react-native-menu/menu@expo/ui/community/menuAndroid / iOS / Expo Go
@gorhom/bottom-sheet@expo/ui/community/bottom-sheetAndroid / iOS / Web / Expo Go

All eight import paths appear as ./community/... entries in the exports map of @expo/ui 58.0.28 on npm. To check the version you actually have, node -p "Object.keys(require('@expo/ui/package.json').exports)" lists them.

This table answers one question: does a replacement exist? It says nothing about whether swapping to it shrinks your dependency list. That second question has a different answer in every project.

If your motivation is "I want this screen to look like the OS," the first question is enough. If your motivation is "I want fewer native dependencies so that fewer things break on every SDK bump," you need the second one answered before you estimate the work. Mine was the second.

peerDependencies do not show up in a package.json grep

Manual verification usually looks like this:

grep react-native-pager-view package.json
# "react-native-pager-view": "^10.0.2"

One direct dependency. One screen using it. It reads as removable.

In reality react-native-tab-view requires it, and the requirement is not written where you are looking:

// react-native-tab-view@4.3.4 package.json (excerpt, latest as of November 2026)
{
  "dependencies": {
    "use-latest-callback": "^0.2.4"
  },
  "peerDependencies": {
    "react": ">= 18.2.0",
    "react-native": "*",
    "react-native-pager-view": ">= 6.0.0"
  }
}

A peer dependency says "I will not install this, but I assume it is there." If you use React Navigation's material top tabs, react-native-tab-view is in your tree, so react-native-pager-view stays. You could convert every one of your own screens to Expo UI and still remove exactly zero npm packages.

It goes one level further. @react-navigation/material-top-tabs 7.8.1 lists react-native-pager-view: ">= 6.0.0" in its own peerDependencies too, so the requirement reaches you from two directions. Removing either holder alone changes nothing.

That was the trap. Whether a swap removes anything is decided not by the package you are replacing, but by whatever else declares it as a peer.

If you only want to check one package before writing any script, npm already has a reverse lookup:

npm explain react-native-pager-view
# lines that start with "peer" are peer requirements

npm explain walks back through why a package is installed, peer edges included. It answers one package at a time, though, which makes it awkward when you want all eight side by side to decide where to start. Hence the script below.

✦

Thank you for reading this far.

Continue Reading

What follows includes implementation code, benchmarks, and practical content we hope you'll find useful. This site runs without ads — server and development costs are supported entirely by members like you. If it's been helpful, we'd be truly grateful for your support.

WHAT YOU'LL LEARN
✦You will be able to tell, with a single command, which of the eight Expo UI replacements actually remove a dependency from your specific project
✦You will catch the dependencies that survive the swap through peerDependencies before you spend an afternoon on the migration
✦If you share components across several apps, you will be able to pick which app and which screen to start with based on the dependency graph rather than a guess
Secure payment via Stripe · Cancel anytime
✦

Unlock This Article

Get full access to the rest of this article. Buy once, read anytime. This site is ad-free — your support goes directly toward keeping it running.

or
Unlock all articles with Membership →
Share

Thank You for Reading

Rork Lab is ad-free, supported entirely by members like you. We publish practical guides daily with implementation code, benchmarks, and production-ready patterns. If you've found it useful, we'd love to have you on board.

  • ✦Copy-paste ready implementation code
  • ✦New advanced guides published daily
  • ✦$5/mo or $10 for lifetime access
View Membership →

Related Articles

⬡ Dev Tools2026-10-25
Sound Effects Stop at Play #40 — With expo-audio's createAudioPlayer, remove() Alone Isn't Cleanup
Creating a createAudioPlayer instance per play in expo-audio can leave Android silent after about 40 plays, with didJustFinish never arriving. What remove() and release() each do, three ways to restructure, and how to notice when it happens.
⬡ Dev Tools2026-09-10
I Added a Dim Screen Button, and iPhones Stayed Dark After the App Was Closed
In expo-brightness, setBrightnessAsync applies only to the current activity on Android, but changes the device brightness itself on iOS. Here is why the cleanup burden falls on one platform only, and a hook that restores brightness through AppState.
⬡ Dev Tools2026-09-04
EAS secret visibility does not keep a value out of your app — deciding prefix and visibility separately
The EXPO_PUBLIC_ prefix decides what ships inside your app; EAS visibility decides who can read it. Why stacking them blanks a value on OTA updates, and how to check your build.