Jonathan Bones

One thing to watch out for though was using react-native Pressables in portals. Switching these out to react-native-gesture-handler Pressables meant the press event handlers were fired correctly.

Nice! Adding it to our project this evening was really simple and since the naming is consistent with gorhom portal I only had to update the imports and add StyleSheet.absoluteFillObject to the PortalHosts and we were good to go. 🚀

Huge thanks to @expo.dev for featuring our journey with DEPOT on their blog! Big thank you as well to @baumstumpf.bsky.social for the editorial support 🙏
The path to success was built one step at a time - and those incremental improvements compounded to really pay off. 🚀

React Native Radio - RNR 352 - Expo Launch with Cedric van Putten Mazen and Robin welcome back Cedric van Putten to discuss Expo Launch, a new tool that automates deploying React Native apps to the App Store. Learn how Expo is streamlining certificates, screenshots,...

🖤❤️ RNR 352 ❤️🖤

This week: @expo.dev Launch! 🚀

Our hosts @mazenchami.dev and @robinheinze.dev welcome back @cedric.dev to break down how Expo's new tool is making it easier than ever to launch to the App Store!

Listen now 👇
infinite.red/react-native...

Vercel now supports the Bun Runtime Deploy and run your applications with Bun's fast JavaScript runtime on Vercel Functions, with full access to Bun APIs and improved performance

Vercel added Bun runtime support (Beta): Next.js apps can now access native Bun APIs like Bun.file 🎉 To enable, declare the bunVersion in your vercel.json e.g.
`"bunVersion": "1.x"`
bun.com/blog/vercel-...

pnpm 10.21 | pnpm Added support for Node.js runtime installation for dependencies and a setting for configuring trust policy.

pnpm 10.21 now auto-installs the correct Node.js runtime for deps that declare engines.runtime, improving compatibility for CLI tools.
pnpm.io/blog/release...

Error chaining in JavaScript: cleaner debugging with Error.cause - Matt Smith Use JavaScript's 'cause' property to chain errors, preserve context, and simplify debugging. Cleaner stack traces, better test assertions.

Error.cause (ES2022) helps to add clearer error context and preserve the original stack trace. I wasn't aware of this property, so many thanks to Matt Smith - looking forward to trying it out!
allthingssmitty.com/2025/11/10/e...

TanStack DB 0.5 — Query-Driven Sync | TanStack Blog You don't need a new API for every component. With 0.5, the component's query is the API call. tsx // Your component's query... const { data: projectTodos } = useLiveQuery((q) = q .from({ todos }) .jo...

TanStack DB dropped Query-Driven Sync in v0.5 and introduced `syncMode: "on-demand"`, which removes the need to load full datasets upfront. 🔥
tanstack.com/blog/tanstac...

Here are a few dev highlights, I came across this weekend 👓☕️ Give them a skim on your next coffee break — and let me know what you think 👇

I'm preparing my Star Wars themed talk on TanStack DB for next week's React(Native) Kiel meetup. If you're around in Kiel on Monday evening, feel free to join us for some nerdy fun! ⚛️
www.meetup.com/kiel-react-n...

GitHub - expo/examples: Example projects that demonstrate how to use Expo APIs and integrate Expo with other popular tools Example projects that demonstrate how to use Expo APIs and integrate Expo with other popular tools - expo/examples

The Expo examples repo is a super helpful resource for testing out app ideas. There’s a bunch of examples of modern setups that you can use as a starting point. Helps me move fast on ideas rather than getting stuck in setup decisions. github.com/expo/examples

🏆 After a week of research and hours of passionate debate we have trimmed 1,200 apps down to 6 nominees for each of the App Award categories.

If you are looking for inspiration to elevate your app, you can find it here: expo.dev/awards

Congrats to all the nominees!

Always fun seeing how the ecosystem evolves and if you've come across anything else worth reading, post it below - I'd love to check it out. 📖🤓

Upgrade to Solito 5 | Solito Solito 5 drops react-native-web as a dependency. It now works with zero special configuration on Web. On iOS and Android, nothing has changed.

5. solito.dev/v5

Solito v5 has landed - now with zero web config and dropping react-native-web as a dependency. A notable shift for universal app setups and something I'll be keeping an eye on to see how this evolves.

One Year with Next.js App Router — Why We're Moving On A critique of React Server Components and Next.js 15.

4. paperclover.net/blog/webdev/...

Interesting reflections on working with the app router. Not sure I agree with every take but it's great to see TanStack Start gaining traction in the community - something I've used in hobby projects but not yet in production.

Rethinking async loops in JavaScript - Matt Smith Struggling with 'await' in loops? Explore common mistakes and modern solutions to optimize async code for performance.

3. allthingssmitty.com/2025/10/20/r...

Clear, practical examples for managing async work in loops. Presents a solid framework for handling concurrency without getting tangled in nested promises.

URLPattern is now Baseline Newly available  |  Blog  |  web.dev URLPattern became Baseline Newly available as of September 15, 2025.

2. web.dev/blog/baselin...

The URLPattern API is now baseline, newly available meaning less manual regex maintenance - a quiet but meaningful win for readability too.

const pattern = new URLPattern({ pathname: "/users/:id" });
const isMatch = pattern.test(location.href);

How to Fix Any Bug — overreacted The joys of vibecoding.

1. overreacted.io/how-to-fix-a...

A great post on effective debugging. Focuses on isolating the real issue instead of chasing noise or false positives - simple advice that saves time in practice.

Here are some interesting dev reads I stumbled across this week - a mix of practical updates, thoughtful perspectives and a few things that made me rethink familiar patterns. 🧵⚛️

The paid plans give you some nice extras such as priority builds and a higher number of eas update users out of the box but honestly you get access to all features with the free plan. The great thing is that there’s no vendor lock-in either so if you want to build locally instead, you can too.

That’s awesome! Great to see that both paid and free users benefit from the increased capacity too. 💪

🕕 When: Monday, Aug 25th - doors open 6pm
📍 Where: Fleet 7 (Baubüro), Kiel
Come by for the talks, stay for the drinks & conversations. See you there! 🚀
#React #ReactNative #Kiel

• Vim-Motions - Unlock hidden superpowers to boost your efficiency in Vim
• React Native Skia - High-performance 2D rendering + a peek into shaders

React(Native) Meetup #29, Mon, Aug 25, 2025, 6:30 PM | Meetup Welcome to the 29th React(Native) Meetup Kiel. Everyone is welcome to join us, whatever your experience with React or other web technologies. Since the number of spots is l

📣 The next edition of React(Native) Kiel is coming up next Monday, Aug. 25th! I’ll be co-hosting with @dbanck.com & @baumstumpf.bsky.social and we’ve lined up two talks you won’t want to miss 👇
www.meetup.com/kiel-react-n...

Ah thanks - that’s a great shout! I like the flexibility DOM components offer for gradual adoption of native (where needed / desired) but apart from a few simple PoCs I haven’t used them in production yet… maybe now’s the time 🚀

Still, for some use cases the WebView approach is maybe “good enough”:

✅ Feature parity with web
✅ Fast time to market
✅ OTA updates baked in by design

But is short time speed worth the cost of long-term UX debt? Feel free to comment and let me know what you think 💭

My take: React Native wins long-term for the following reasons:

📱 Truly native components & feel
🚀 Better overall performance
🌐 Reliable offline support
🎲 Fewer risks regarding app store guidelines

Hey #ReactNative community 👋 I've faced the following question a number of times: WebView wrapper of existing website (with native navigation shell) vs. full React Native adoption. Given tight budgets and sometimes limited resources, it’s not always easy. I’m curious to hear your thoughts 🧵👇

Oof, good luck! 😅☕️ If you can, I’d suggest adopting @expo.dev prebuild. It depends on your native libs and config plugin support, but it massively cuts down maintenance pain - especially on long-lived projects. Saved us countless hours already. 🚀

Tools for development An overview of Expo tools and websites that will help you during various aspects of your project-building journey.

You might find the expo-doctor package helpful - it checks whether the expo modules and 3rd party deps are compatible with the installed SDK version. Not sure if that’s what you were looking for but hope it helps! docs.expo.dev/develop/tool...