[tsapeta]

Why

Update to the latest expo-modules-macros.

Two packages depended on it with different versions: expo-modules-core pinned 0.19.1 (the macros the iOS build compiles with), and expo-modules-cli had its own ^0.16.0 (the scanner for generate-types). So the CLI could read the Swift sources differently from the macros that build them, and every bump had to touch both. This PR makes expo-modules-core the single source of the version.

Changes in expo-modules-macros since 0.19.1

• Bind @JS functions and setters that return nothing through the Void overload of setProperty, so they no longer build and write an undefined value on each call. The overload is already in expo-modules-jsi on main. (Bind @JS functions and setters that return nothing through the Void overload expo-modules-macros#81)
• Report an error on closure types in @Record properties and in @Event and @Union payloads. Before, the expansion produced invalid Swift and the compiler reported errors inside it. (Report closure types in @Record properties and @Event and @Union payloads expo-modules-macros#80)
• scan-exports reports platforms (from #if and @available), deprecations, access levels and default values. constructorParameters is replaced by initializer, and the schema version is now 8. (Report platforms, deprecations, access levels, and default values in scan-exports expo-modules-macros#79)
• scanModules and scanExports take a timeout option, the wrapper closes the scanner's stdin, and ScannerError messages name only the binary and the subcommand. (Add a timeout option to the scanner wrapper expo-modules-macros#78)

The CLI was still on 0.16.0, so it also picks up schema 7 (expo/expo-modules-macros#73): types nested in other types are reported under qualified names, such as DigestOptions.Encoding.

How

expo-modules-core

Bumped expo-modules-macros from 0.19.1 to 0.20.0.

expo-modules-cli

• expo-modules-macros is no longer a dependency, only a devDependency for its types and tests. expo is a peer dependency, which every Expo module already declares.
• resolveMacros loads the wrapper and the scanner by resolving expo from the scanned package, then expo-modules-core from expo, then expo-modules-macros from core. This goes through expo because a module reaches core only through it. Autolinking and the SPM plugin resolve the macros from core as well, so the scan and the build use the same version.
• The CLI renders schema 8 (SCAN_EXPORTS_SCHEMA_VERSION). When the resolved macros report another schema, it fails with a message that names the version and its path. A test keeps the constant equal to the devDependency's.
• Schema 8: the shared object constructor comes from initializer.parameters.
• Schema 7: an enum, record, or union nested in another type is declared under its last name component (Encoding), the way JS sees a nested shared object by default. Refs resolve through the qualified name. A clash with another declaration is skipped with the existing warning.
• The render tests write their surfaces without platforms and add them in a render helper, since the renderer doesn't read them yet.

Test Plan

• expo-modules-cli: tsc, oxlint and jest pass (89 tests), including new tests for the resolution, the schema mismatch and nested names. A package without expo fails with the "Could not resolve expo" message in plain Node. Jest's resolver falls back to the workspace expo, so this case has no Jest test.
• Ran the built CLI on expo-haptics, expo-crypto and expo-application with the real 0.20.0 scanner. The nested enums that rendered as unknown before are now declared: NotificationType and ImpactStyle in expo-haptics, Encoding in expo-crypto's DigestOptions.
• expo-modules-core: CI.

[expo-bot]

The Pull Request introduced fingerprint changes against the base commit: 12d0a9f

Fingerprint diff

[
  {
    "op": "changed",
    "beforeSource": {
      "type": "dir",
      "filePath": "../../packages/expo-modules-core",
      "reasons": [
        "expoAutolinkingIos",
        "expoAutolinkingAndroid",
        "expoAutolinkingIos"
      ],
      "hash": "2165f47e763aaee5e9652ab5ab4260a418b6fd23"
    },
    "afterSource": {
      "type": "dir",
      "filePath": "../../packages/expo-modules-core",
      "reasons": [
        "expoAutolinkingIos",
        "expoAutolinkingAndroid",
        "expoAutolinkingIos"
      ],
      "hash": "83837d8cbe8091b867d03b9fed101ef200424dde"
    }
  }
]

---

Generated by PR labeler 🤖

[expo-bot]

Hi there! 👋 I'm a bot whose goal is to ensure your contributions meet our guidelines.

I've found some issues in your pull request that should be addressed (click on them for more details) 👇

⚠️ Suggestion: Changesets release policy on main

Minor releases may not be accepted during a beta period. Use patch instead.

• .changeset/expo-modules-cli-macros-from-core.md

---

Generated by ExpoBot 🤖 against 8042465

[github-actions]

Subscribed to pull request

File Patterns	Mentions
packages/expo-modules-core/**	@Kudo, @lukmccall

Generated by CodeMention