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

How to share one native build across agents on JS-only branches with Simfleet

Cache native builds by fingerprint so many agents reuse one build and environment switches skip native rebuilds.

Who it is forA team lead or platform engineer whose coding agents run many JS-only branches and keep triggering slow native rebuilds.

The problemEvery branch or environment switch can force a fresh native build, which wastes time and machine resources when only JavaScript changed.

The outcomeNative inputs are fingerprinted with JavaScript excluded, so agents on JS-only branches share one build, and switching staging and production does not rebuild native code.

What you need first

  • A Mac running macOS
  • Bun 1.1 or newer (https://bun.sh)
  • Xcode for iOS work, plus `brew install mobai-app/tap/simslim baguette watchman`
  • Android SDK with platform-tools and emulator for Android work, plus `brew tap kdbhalala/avdslim https://github.com/kdbhalala/avdslim.git && brew install avdslim scrcpy`
  • A React Native or Expo app with a Git repository

Steps

  1. bun add -d simfleet
  2. Add buildCacheProvider: { plugin: require.resolve("simfleet/build-cache") } under experiments in app.config.js (inferred from the README snippet).
  3. simfleet native plan
  4. simfleet native ensure (inferred, check the README)

Prompt for your agent

Using the simfleet repo (entropyconquers/simfleet), set up the Expo build cache in <path-to-app> and run `simfleet native plan` to inspect the fingerprint. Expected output: a plan that lists the native inputs and whether a cached build exists. Verify that changing only a JavaScript file leaves the native fingerprint unchanged.

Caveat. Only `projectName`, `nativeAuth`, and `nativeShells` feed the native fingerprint, so native changes outside those settings may not be detected as expected.

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