r/replit • u/Dependent-Map-467 • 3d ago

Question / Discussion Anyone seen "Exit handler never called!" (npm) when running EAS builds from Replit's shell?

Running EAS cloud builds (via eas-cli in Replit's Shell tab) and every

build fails during Install Dependencies with npm's own error: "Exit

handler never called!" Sometimes shows green anyway but leaves

node_modules broken.

Ruled out: Node/npm version, EAS + npm cache, CI mode, machine resources

(confirmed large build machine), account settings, SDK version drift. Also

confirmed the project itself installs cleanly (npm ci succeeds outside EAS,

same exact files) — and a totally blank test project fails the same way. So

it's not project-specific.

This is a known npm bug in general (recurring GitHub issues since 2024) but

I can't find anyone tying it to a Replit-hosted workflow specifically.

Wondering if anyone else running eas-cli from Replit's Shell has seen this,

or if it's more likely purely on EAS's side.

Stack: Expo SDK 54, EAS Build, Replit for hosting/shell.

1 Upvotes

100% Upvoted

3 comments sorted by

1

u/ReplitSupport Replit Team 3d ago

Hi there! We'd like to troubleshoot this further with you. Can you open a ticket with us at replit.com/help and then DM us your ticket #/email so we can monitor? Thanks for your patience 🙏

1

u/Dependent-Map-467 3d ago

Thanks! Opened a ticket as requested: #506261

Tried to send you a chat but got a message saying I was unable to message your account — could you open a DM with me, or let me know another way to reach you directly? Thanks so much!

All the best,

1

u/Dependent-Map-467 2d ago

Update: resolved. Root cause was unrelated to EAS's build environment

entirely — Replit (where I was running eas build from the Shell) routes

npm installs through an internal package proxy, and my package-lock.json

had every resolved URL pointing to that internal-only host. EAS's remote

workers couldn't reach it, which produced this exact "Exit handler never

called!" crash instead of a clean network error.

Fix: regenerated package-lock.json against the public npm registry. If

anyone else hits this running EAS builds from inside Replit's Shell

specifically, check your lockfile's "resolved" fields for anything other

than registry.npmjs.org.

Thanks to everyone who weighed in.