On Tuesday, October 27, React Native 0.88.1 landed with a change I have wanted since the SwiftPM work started: spm add and spm update now write React Native’s build settings to a generated xcconfig and its scripts to a folder, so bumping the framework version no longer rewrites project.pbxproj. Anyone who has resolved a pbxproj merge conflict at 11pm knows why that line matters more than the headline features in most minors. The same week Node.js 26 became an LTS release, Node 27 showed up as an alpha with V8 15.6, and a benchmark post about which JavaScript frameworks agents handle well hit the top of Hacker News. Quiet week on react.dev. Busy week everywhere else.
Here is what mattered in React and React Native for October 26 to November 1, 2026.
Releases
React Native 0.88.1: SwiftPM settings leave your pbxproj
0.88.1 is a patch, but a thick one. On iOS, React Native’s C, C++ and Objective-C code is now compiled with -O2 instead of -Os in Release, and Yoga and glog use -O2 in every build, matching what Android already did. The SwiftPM commands write settings to ReactNativeSPM/ReactNativeSPM.xcconfig and scripts to ReactNativeSPM/Scripts/; if your own xcconfig hides a React Native value you must add $(inherited), and the tool prints the exact fix. Also in: a Yoga flex-shrink fix for positive float residuals, text nodes keeping their measured pixel size when snapped to the grid, Text without a background no longer painting a transparent one, three JSI forwarding fixes from Marc Rousavy for runtime decorators, and an Android fix for text measured at the wrong width when fontVariationSettings hit a reused Paint. If you adopted fontVariationSettings from 0.88.0 and saw clipped text on Android, this is your patch. Note the repository URL: releases now live under github.com/react/react-native, the React Foundation org, which our Upgrade Helper guide from Friday already points at.
Node.js 26 goes LTS, Node 27 alpha brings V8 15.6
Node 26.13.0 marks the 26.x line as Long Term Support, codename Lithium, supported to the end of April 2029. It carries no code changes over 26.12.1, so this is a metadata release and a calendar event: your CI matrix and your engines field can move. One day later 27.0.0-alpha.0 appeared with V8 15.6: Math.sumPrecise(), Iterator.zip(), Iterator.prototype.join() on by default, import defer behind a flag, and a new default heap limit of half the physical memory clamped between 256 MB and 4 GB, with Buffer memory now counted toward it. That last one will surprise a Metro or Jest run that used to squeak by. Set --max-old-space-size explicitly before you find out in CI.
Expo SDK 58 patch wave, EAS CLI 26 and 27
Expo pushed a coordinated patch set on October 31 (expo 58.0.22, expo-router 58.0.29, expo-modules-core 58.0.29, expo-updates 58.0.20, expo-dev-client 58.0.18, @expo/ui 58.0.26 and about twenty more). No changelog post this week; the last entries are the SDK 58 release and the native crash reporting in EAS Observe from earlier in October. EAS CLI went from 25 to 26.0.0 (breaking: legacy artifact type exports removed, workflow uploads routed through workflow storage), then 27.1.0 (queued workflow runs shown by workflow:status, and the CLI now fails instead of continuing when it cannot pull environment variables, which is the correct behaviour and will break a few pipelines that silently relied on empty env) and 27.2.0 with eas observe:traces and eas observe:trace for span trees in the terminal. Two majors in five days is fast even for Expo. Pin the CLI in your workflow files.
Library corner
React Native Paper 6.0.0-alpha.1 is the first 6.x prerelease since June: 41 commits, 11 breaking, with the accessibility props moving to aria-label, role and friends. Our Paper guide stays on 5.x until beta. Unistyles 3.7.0 supports the 0.88 style props, adds a Unistyles track to DevTools performance traces, and ships one breaking change: UnistylesRuntime.themeName now always returns the app theme, not the scoped one. Skia 3.8.1 fixes source alpha in plusLighter and plusDarker, Skottie crashes on unnamed layers, and fontVariations in TextStyle on native. react-native-screens 4.30.1 stops leaving an iOS navigation bar at alpha == 0 and adds RNSNavigationItemCustomizerProtocol for SplitView columns. React Native ExecuTorch 0.11.0 moves LLM generation onto TypeScript runners with a llama.cpp-style sampler and constrained decoding, re-exports models with 16k context windows, and adds depth estimation (Depth Anything V2 and V3) and MI-GAN inpainting. On-device inference in RN is now a real product category, not a demo. Also: Nativewind 5.0.0-rc.1 (pinned to react-native-css 3.1.0-rc.1 and Expo 57; latest is still v4), Metro 0.87.2 with a metro:runtime/* specifier and two resolver fixes, Worklets 0.13.1, VisionCamera 5.2.4 (tap-to-focus and zoom gesture listeners), Sentry React Native 8.33.0 (compiled to ES2018 for a smaller bundle, Android fatal JS envelopes now persisted before the process exits), Stream Chat RN 9.11 with voice-agent visualizations, keyboard-controller 1.22.9, React Router 8.5.1 and TanStack Query 5.105.1.
News
Which frameworks do agents actually handle well?
Nolan Lawson wrote The AI cost of JavaScript frameworks, a benchmark where coding agents build the same small Pokemon app in several frameworks, and it sat at the top of Hacker News on Sunday with over three hundred points. His complaint is the one I share: teams are rewriting frontends because a framework is “better for agents” with no evidence either way. The post has evidence. Read it before your next architecture meeting, whatever it says about your stack.
Shopify’s native move, seven weeks on
The r/reactnative Layoffs and hiring thread is the most honest reading of the week, and the Shopify decision from September still shadows every reply. My view has not changed since digest #5: a company with hundreds of mobile engineers reweighing “build twice with agents” against “build once with a framework” tells you about their cost structure, not yours. Friday’s post on this site goes through the whole state-of-the-ecosystem question properly, with numbers.
Worth reading
From r/reactnative: Speedrun, an open-source E2E runner that executes Maestro flows in parallel; a React Native plus Rust integration through C++17, JSI and TurboModules; “To my past self who wrote image: latest”, an iOS 27 launch crash caused by an unpinned EAS build image, which is the whole argument for pinning in one post; a CapCut alternative built entirely in React Native with no cloud; and This Week In React Native #303 for a second curation. From r/reactjs: the Redux Toolkit v3 roadmap and a good argument in Did you remove your useMemo calls after turning on the React Compiler? (most people did not, and most people are right to wait).
react.dev stayed quiet for a seventh week; the last post is still React 19.3 from September. On this site this week: error tracking with Sentry and its alternatives on Wednesday, and the state of the React Native ecosystem on Friday. If you shipped something I missed, tell me in the comments and it goes in next Monday.