DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to trace React Native calls into native Swift, Kotlin or Objective-C with BGTS Context Engine

Find the native method behind a NativeModules call in a React Native or Expo app.

Who it is forA developer on a React Native or Expo app who needs to find the native implementation behind a TypeScript call.

The problemNo single parser can see a call that crosses from TypeScript into Objective-C, Swift or Kotlin, so the native side is easy to miss.

The outcomeThe context answer links the NativeModules call in TypeScript to the native method it reaches.

What you need first

  • Docker with Docker Compose, to run PostgreSQL 16 with Apache AGE and pgvector
  • Python with pip
  • A local repository to index
  • A coding agent that can call MCP tools, or the bce command line

Steps

  1. docker compose -f deploy/docker-compose.yml up -d
  2. pip install bgts-context-engine
  3. bce migrate
  4. bce index --repo /path/to/your/react-native-app --name my-app (inferred, check the README)
  5. bce context --task "where does NativeModules.Foo.bar() end up on the native side" (inferred, check the README)

Prompt for your agent

Using the bgts-context-engine repository, index the React Native app at <target repo path>, then run bce context with the task <question about a NativeModules call>. Expected output: a ranked answer that includes the native Objective-C, Swift or Kotlin method. Verify that the native method is linked from the TypeScript call site.

Caveat. The README describes these bridges for React Native and Expo only, so other cross-language calls may not be linked.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page