Node.js version in `.nvmrc` does not satisfy `engines.node`

New Issue Checklist

• Report security issues confidentially.
• Any contribution is under this license.
• Before posting search existing issues.

Issue Description

.nvmrc pins Node.js 20.15.0, which is below the minimum Node.js version declared in engines.node of package.json (>=20.19.0 <21.0.0 || >=22.13.0 <23.0.0 || >=24.11.0 <25.0.0). Developers who run nvm use in the repository get a Node.js version that Parse Server does not support.

Several dependencies already require at least Node.js 20.19.0, for example:

• @noble/hashes 2.0.1 (production): >= 20.19.0
• eslint-plugin-expect-type 0.7.0 (development): ^20.19.0 || >=22.12.0

CI is not affected because it does not read .nvmrc.

This came up in the review of #10697.

Steps to reproduce

1. Check out alpha.
2. Run nvm use; Node.js 20.15.0 is selected.
3. Run npm ci; npm warns about unsupported engines.

Actual Outcome

.nvmrc selects Node.js 20.15.0, which does not satisfy engines.node.

Expected Outcome

.nvmrc selects a Node.js version that satisfies engines.node and the engine requirements of the dependencies, e.g. a current Node.js 20.19.x or newer LTS release.

Environment

Server

• Parse Server version: 9.10.2-alpha.4 (alpha branch)
• Operating system: any
• Local or remote host: local development

Database

• Not applicable

Client

• Not applicable

Logs

Not applicable