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 🧵

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

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)

there's also an experiment that allows you to auto-resolve issues with duplicate native module dependencies or hoisting conflicts (monorepos rejoice!) ✨ flip one flag, and Expo Autolinking also applies its autolinking decisions to Expo's metro bundling

no more metro conflicts, metro config conflicts, expo deps conflicts, react package conflicts, babel conflicts, native module conflicts, ... full write up of how we got here in this blog post: kitten.sh/blog/autolin...