Node.js version in `.nvmrc` does not satisfy `engines.node`
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 92/100
Research direction
Compare the Node.js version in .nvmrc with the engines.node range in package.json and the dependency requirements described in the issue. Update .nvmrc to a compatible version, then run nvm use and npm ci to confirm that the selected version satisfies the declared engines without warnings.
Written by the indexing model from the issue text.
Description
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/hashes2.0.1 (production):>= 20.19.0eslint-plugin-expect-type0.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
- Check out
alpha. - Run
nvm use; Node.js 20.15.0 is selected. - 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(alphabranch) - Operating system: any
- Local or remote host: local development
Database
- Not applicable
Client
- Not applicable
Logs
Not applicable
- Dominant language
- JavaScript
- Stars
- 21.4k
- Forks
- 4.8k
- Avg merge
- 2d 12m
- Merged PRs (30d)
- 47
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from parse-community/parse-server
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
parse-community/parse-server#10720 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
parse-community/parse-server#10710 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
parse-community/parse-server#10634 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
parse-community/parse-server#10631 · 1 comment ·
Maintainers usually reply within 1 day
-
/installations and /audiences reject a find sent as POST + _method=GET with "Invalid key name: 0"Open
Difficulty 2/5 Half a day Newbie friendliness 65/100
parse-community/parse-server#10626 · 1 comment ·
Maintainers usually reply within 1 day
All issues in parse-community/parse-server
Similar issues
-
feature task
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
RealDevSquad/website-www#1178 ·
-
add latest sol modelOpen
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
netlify-labs/nax#56 · 2 comments · 1 reaction ·
-
accessibility bug revealjs
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
quarto-dev/quarto-cli#14961 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
PnX-SI/GeoNature#4435 · 2 comments ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
openlayers/openlayers#17648 ·
Maintainers usually reply within 1 day