Home / Companies / Clerk / Blog / Post Details
Content Deep Dive

Migrating from @clerk/clerk-expo to @clerk/expo: Breaking Changes, Native Components, and the Complete Upgrade Path

Blog post from Clerk

Post Details
Company
Date Published
Author
Roy Anger
Word Count
7,498
Language
English
Hacker News Points
-
Summary

The deprecated @clerk/clerk-expo package has been replaced by @clerk/expo, which comes with Clerk Core 3, featuring native components, platform-native OAuth, passkey support, and offline resilience, offering a 50KB gzipped size reduction through shared React internals. This comprehensive migration guide outlines the steps for Expo developers to transition, including automated upgrades, breaking changes, and new feature adoption. It delves into the updated Core 3 authentication hook API, the introduction of the <Show> component for managing authentication state, and the integration of native components like AuthView and UserButton. The guide also addresses token caching, appearance and theming adjustments, and the experimental nature of passkey and offline support, highlighting the benefits of upgrading for enhanced functionality and performance. With Core 2 supported until January 2027, developers are encouraged to prioritize this upgrade to leverage new capabilities while maintaining compatibility with existing Expo projects.