we run a lot of agents in parallel, each in its own git worktree. almost 500 prs last month from 5 of us turns out react native really doesn't like that the first problem was kind of dumb. every worktree wanted the same ports for metro and our backends. with 1 or 2 agents you can juggle that by hand. past that they start stepping on each other, killing each other's servers or loading the wrong bundle so now each worktree picks its own ports based on its path. i can have one agent on the ios sim, one on the android emulator and one on my actual phone, all at once, and none of them know the others exist the second one was sneakier. metro shares one cache across every checkout on your machine, which is usually fine. but reanimated's worklets plugin writes a file while babel runs. so worktree B gets a cache hit from worktree A, babel gets skipped, that file never exists, and the bundle dies with ENOENT 🫠 moving the cache into each worktree fixed it, and turned up one more bug in metro itself. its file map cache never got saved, so it recrawled the whole repo on every start sent the fix, @robjhogan merged it yesterday 🙏

ships to prod. will ship to mandap 😂 @icantcodefyi built this for me. mom forked it and now is the sole maintainer 😭 marry-shubh.vercel.app/