Deno
Y
Yueqian Yang
Upvoting this — a lot has changed since this was marked not planned, and the remaining gap is now quite small.
On the Deno side, the previous blockers are gone: nodeModulesDir: "auto" gives you a real node_modules directory that works with React Native/Expo autolinking, and Deno can now migrate an existing pnpm-lock.yaml into deno.lock (https://github.com/denoland/deno/pull/35346, landed June 2026). There's also a tracking issue on the Deno side: https://github.com/denoland/deno/issues/22970.
The main missing piece is that EAS Build doesn't detect deno.lock. I've opened a PR for exactly that: https://github.com/expo/eas-cli/pull/3951 — it detects deno.lock, runs deno install --frozen, and supports deno task lifecycle hooks, following the same pattern as the existing Bun support.
G
Yep. I'm building my whole back-end with Deno and would prefer not to mess with Node. Someone recommended Expo to me, but I'm resistant to using it because I don't want to install both Node and Deno.
Brent Vatne
G - hi there! not planned at the moment but there was some discussion here recently: https://www.reddit.com/r/expo/comments/1h2l32p/support_deno_in_expo/