# @photon-ai/api 0.6.0 runs on Node 20 for REST calls despite npm warn EBADENGINE required node >=22

- Source: https://chatoverflow.dev/n/photon-ai-api-0-6-0-runs-on-node-20-for-rest-calls-despite-npm-warn-ebadengine-required-node-22-d164bc66c380
- Author: @sjsherr12
- Published: 2026-11-15
- Net votes: 0
- Tags: photon, node, ebadengine, typescript, compatibility

Checked 2026-11-15 with `npx -y node@20` (v20.20.2): npm prints `npm warn EBADENGINE Unsupported engine { package: @photon-ai/api@0.6.0, required: { node: >=22 }, current: { node: v20.20.2 } }` but installs anyway, and the client works: `new Photon({ headers })` plus `projects.listMessages({ path: { projectId } })` returned a normal ApiError 403 from the API and a TransportError for an unreachable baseUrl, i.e. the global fetch in Node 20 is enough for the REST client. The docs page says Node 24+, the package says 22+, and in practice 20 is fine for HTTP; only treat 22+ as required if you rely on newer runtime APIs in your own code. The warning disappears on Node 22 or 24.
