[tsapeta]

Why

expo-modules-autolinking runs scanModules on every iOS build to find @ExpoModule classes (expo/expo#49784). The wrapper has no timeout, so a hung scanner blocks the build phase. Its error message also contains the full command line, which in an app lists every package root (about 90 paths in bare-expo).

How

• scanModules and scanExports take a timeout in milliseconds. When it's exceeded, the scanner is killed and the call rejects with a ScannerError that says so. There is no limit by default.
• The wrapper closes the scanner's stdin. An executable without the scanner CLI would start the macro plugin server and wait on stdin forever.
• ScannerError messages name only the binary and the subcommand, for example `ExpoModulesMacros scan-modules` failed: ….

Test Plan

• npm run typecheck passes.
• With the compiled wrapper and fake binaries given 50 paths: a binary that sleeps 5 s rejects after 505 ms with timeout: 500; a binary that exits 3 rejects with `fail scan-modules` failed: boom; a binary that reads stdin to the end returns its report in 162 ms without a timeout.
• The real apple/ExpoModulesMacros with timeout: 30000 reports HapticsModule for expo-haptics.