v0.1.0-alpha.4

Versions without surprises

A patch release of Expo or React Native should not need a new rn-xtool release. Expo published 58.0.22 while this release was being prepared, and rn-xtool needed no change for it.

New

• Expo SDK 57 now has a floor. rn-xtool accepts expo 57.0.31 or any newer 57.x. A newer release than the verified one builds with a warning that names the verified versions.
• Bare React Native accepts every patch of a supported minor, starting from these floors: 0.86.x from 0.86.2, 0.87.x from 0.87.1, and 0.88.x from 0.88.0.
• rn-xtool doctor --project checks only the project, without Swift, xtool or a device. It shows:
  • the version line that covers your versions, or the reason none does;
  • which SwiftPM scripts the build would use;
  • whether React Native's prebuilt artifacts are cached, local or published;
  • whether the Expo modules are precompiled;
  • which podspec features your libraries use.

Changed

• On Expo SDK 57 and 58, a package from another SDK's release line (for example expo-modules-core 59.x on SDK 58) now stops the build with a remedy instead of only warning.
• The SwiftPM scripts are chosen from the layout of the installed scripts, not from the version number. Every supported version gets the same scripts as before.

Fixed

• rn-xtool needs Node 22.12 or newer, the minimum its own dependencies declare. doctor checks it.
• A malformed rn-xtool.config.json is named in the error.

Upgrading from alpha.3: nothing to do for most projects. See the CHANGELOG.

Known limits:

• No app icon or splash screen yet.
• The first launch after an install shows "No script URL provided" behind iOS's Local Network prompt: tap Allow, then Reload.

Tested with: xtool 1.23.0, Swift 6.4.1, Expo SDK 57 and 58, React Native 0.86.3, 0.87.1 and 0.88.1.