code-review-react-native

To review React Native plugin pull requests, enforce strict cross-language correctness between TypeScript, Kotlin, and Swift bridge wiring. This ensures public API contracts and native event emitter channel data shapes remain consistent across platforms.

Checking SemVer correctness in React Native native modules involves reviewing pull request diffs to ensure version bumps accurately reflect changes to TypeScript types, Expo config plugin outputs, and native bridge contracts without breaking existing integrations.

Hardcoded fallbacks in Kotlin and Swift native bridges should be blocked because defaults must belong to the layer that owns the contract. Enforcing this prevents risky patterns and maintains long-term codebase cleanliness across native layers.

Handling built artifacts during a React Native plugin code review requires treating lib/ and plugin/build/ directories as regenerated outputs. The review focuses on hand-written sources and escalates issues if generated artifacts are incorrectly modified.

Yes, the code review process verifies NativeEventEmitter channel data array shapes and order. It also protects security-relevant EventIdentifiers obfuscation logic to ensure event and obfuscation integrity across the native bridge.

Yes, you can review Expo config plugin output changes. The review ensures that modifications to generated or built artifacts align correctly with hand-written sources and maintain strict TypeScript, Kotlin, and Swift bridge consistency.