@choubari_@expo that shouldn't be an issue
It's quite common and there shouldn't be any immediate problems, even if you invert the stack structure (and if you do run into a problem let us know)
@choubari_@expo you may have to put the stacks below the tabs. it's a rarer configuration, and reordering the groups also means you may have to be more stringent on separating screens into a separate folder but that should work
probably faster to first test on a fresh template codebase though
thanks to @birch_js, @jmeistrich, and @GroundControl i'm (finally π ) sold on RN for desktop having huge potential
hyped to get some changes merged soon to get another step closer to making this first-class supported in expo β€οΈ
i guess @donadeldev tried to get this bumped up on the devtools todo list for a while but we needed other changes from 54 to ship first to make it possible π
Legend List 3.0 is here! π
β¨ React DOM support
β¨ Even faster, more stable
β¨ Perfect initial scroll
β¨ KeyboardAwareLegendList for chat and AI apps
β¨ Reanimated item transitions
β¨ So much more!
Itβs been almost 1,000 commits since v2, super excited to finally release it!
@ArmanHadi386902@expo@swmansion a lot of the value of multiple integrations compound here, and Expo MCP closes gaps (with more to come)
you could let an agent get crash info from Testflight, let it cross-reference that to build or workflow logs, and *then* let it chain & try to repro with Argent or agent-device
π Expo UI is now stable in SDK 56.
One import from @expo/ui gives you SwiftUI on iOS and Jetpack Compose on Android. Real platform components underneath.
Drop-in replacements for 7 common community packages are in there too. Worth thinning out your package.json this week.
Full blog with details about getting started below β
@wiicoin15@expo which deps are you using that aren't on new arch yet? we kept track of them, but think we reached a critical mass a longer while ago. are the left over ones causing you issues in or out of maintenance?
@zoontek i jest but imo i've dedicated a few sections on my post on the original autolinking changes on what we got wrong in expo/expo too https://t.co/p1KNvugpxA
and isolated prevents all of that neatly from ever being a problem
@zoontek if that's ever been an issue, strong indicator thing's have been done wrong π so no, encouraging that by default over improved workflows isn't great, since it can be toggled to go back to "just keep things in a semi-broken state"
tl;dr, is it fun being wrong? π
and (small note in the post) with Expo 56 you can try out our virtual global store support (bun/pnpm) ππ₯³
really useful for creating many worktrees quickly & with low storage impact
Expo SDK 56 is here π
Massive performance improvements for Expo CLI β especially in sandboxes and with agents!
⬦ JS exports are ~20% faster
⬦ iOS builds are now ~1 minute faster
⬦ Android builds are ~2.8x faster
@de_priceles@expo if you mean "expo start" is taking long to be ready, if you haven't tried out SDK 56 yet, it should be faster there https://t.co/rjWrA4tUIT
@IbrahimElkamali@expo neat! ππ
small nit (can't find it on the builder to verify rn, sorry π ),
with "Expo + Bare" I'm assuming you're referring to the styling, but that conflicts with "Bare Workflow" usually referring to no CNG or Prebuild (meaning committed, unmanaged native folders)