Post

there's a lot of exciting things going on in SDK 54, but the less exciting changes will hopefully make your upgrade smoother and your everyday DX with dependencies more stable πŸ’• All kinds of reliability improvements land in SDK 54! small thread about those 🧡

Expo@expo.dev

𝝠 Expo SDK 54 is LIVE πŸš€ β—† React Native 0.81 β—† Precompiled RN for iOS β†’ faster clean builds β—† iOS 26 Liquid Glass icons + views β—† Android 16 target, edge-to-edge default β—† Router v6 native tabs β—† Updates: header overrides, progress, reload screen β—† So much more... expo.dev/changelog/sd...

2 reposts19 likes

Phil, can I just say in the late two weeks I've been on countless trips and you are contributing or in the mix on all of them. Keep up the great work, I don't know how you do it. From gql tada to expo tooling or wherever, well done!

It's really been great on our project. The colocation has helped us write composable UI and it's only getting better as we have completed `tada-ified` the application. One thing I'd love to get a better handle on is properly structuring tests with all the fragments

a lot of implicit deps chains are fixed. One example, if something else depends on Metro that won't break Expo in any case anymore (Pictured: @expo/metro-config's deps graph. And yes, we're also working on reducing deps continuously, more news on that soon)

we also fixed some trickier edge cases, for example: - the fallback resolver means some implicit shared deps are automatically fixed up in our Metro builds (e.g. expo-asset) - a new "supervisor worker" makes sure custom transformers can't break deps chains either github.com/expo/expo/bl...

Autolinking will also work much more like "what you see is what you get" with transitive linking for RN modules, better duplicate detection, better hoisting conflict detection, etc this also means we can safely expand our official package manager support!

Expo Autolinking is more transparent and consistent now. Both expo-doctor and the expo-modules-autolinking verify command can now consistently highlight issues with duplicate dependencies πŸ‘€πŸ•΅οΈ (the screenshot here shows the output that Bluesky gets for debugging, for example)