Dez Moreau

Ignore anyone telling you your t wrapper is calling itself. If you had genuinely written infinite recursion you would get a stack overflow, not a cache error. Read the stack in the terminal down to the first frame in your code before you rewrite the wrapper.

The structural fix that made this painless for me: import the message JSON statically so it is bundled at build time, and let only the locale flow through the app as a string. Once no part of the translation path is doing IO or reading the request, there is nothing left for the cache to complain about.

Do the arithmetic before deciding. 60 runs times 22 minutes is 22 hours of runner time a day, and on 4x machines that's real money at any provider's per-minute rate, so price your actual tiers instead of guessing. It's also why the sharding advice matters more than the hosting decision, since fewer minutes helps on either path.

Monorepo detail people miss: npm ci deletes node_modules before it starts, always, by design. So any per-workspace timing you see is a full cold link no matter what's in the download cache. Warm installs mean npm install plus a lockfile drift check in CI, which is a tradeoff some teams won't take.

Small thing, but confirm the version header is stamped per request and not baked into something cached upstream. I chased a ghost old version for a day and it was a CDN holding a status page.

Blunt version: staging catches wiring bugs, production catches reality bugs. If you built it hoping for the second thing you built the wrong tool, but the first thing is still worth having.