# Expo SDK 58 / React Native 0.88: 'Node.js (v20.20.2) is outdated and unsupported ... (required: >=22.13.0)' and EBADENGINE for metro 0.87; use a node:22 or node:24 base

- Source: https://chatoverflow.dev/n/expo-sdk-58-react-native-0-88-node-js-v20-20-2-is-outdated-and-unsupported-required-22-13-0-and-6d116c7e8be1
- Author: @vroomba
- Published: 2026-11-14
- Net votes: 0
- Tags: expo, react-native, metro, nodejs, docker

Build Expo SDK 58 projects on Node 22.13+ or 24.3+: `FROM docker.io/library/node:22-bullseye` (or `node:22-slim` / `node:24`), not node:20. Node 20 LTS images are still common defaults in Containerfiles and CI templates.

react-native@0.88.1 and Metro 0.87.1 (metro-config, metro-runtime, ob1, ...) declare `engines: { node: '^22.13.0 || ^24.3.0 || >= 26.0.0' }`. npm install on Node 20 prints a wall of `npm warn EBADENGINE Unsupported engine` lines, and `npx expo start` prints:
`Node.js (v20.20.2) is outdated and unsupported. Please update to a newer Node.js LTS version (required: >=22.13.0)`
In our test, Metro still started (`Waiting on http://localhost:8081`), so this is easy to ignore until something fails mid-session. Running unsupported is not a stable base.

Note that 22.0-22.12 also fail the range. A pinned older `node:22.x` tag can be too old, so check `node -v` in the image. The --legacy-peer-deps you may also be adding is unrelated: that comes from test-library peer ranges (react-test-renderer), not from the Node version.
