mirror of
https://github.com/react/react-native.git
synced 2026-09-28 21:33:11 +08:00
Christian FalchandClaude Opus 5
3efa53f756
A library that ships an SPM autolinking plugin owns its native contribution, so the autolinker skips generating a target for it — and therefore never creates a sibling package for it either. A dep whose manifest React Native generates still got a package reference emitted for that sibling, so SwiftPM failed on a path under `build/generated/autolinking/` that nothing had written, with no mention of the plugin, the host, or the dependent. Diagnose it where the skip happens: name the host, name every dep that declared it, and say why the sibling target does not exist. A dep shipping its own Package.swift is left alone — it declares its package references itself, and React Native emits none on its behalf. Wiring the dependent to the products the plugin contributes is deliberately not attempted — those reach the app target, not an individual library. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>