parse-community / parse-community/parse-server
npm i parse-server installs outdated version 4.10.20 by default
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 21.4k
- Forks
- 4.8k
- Avg merge
- 7h 45m
- Merged PRs (30d)
- 11
Description
Issue Description
When running npm i parse-server the version that gets installed is 4.10.20
Steps to reproduce
npm i parse-server
npm list | grep parse-server
Actual Outcome
└── parse-server@4.10.20
Expected Outcome
Latest version within the package.json version range.
Older version is causing 50 vulnerabilities (6 low, 10 moderate, 25 high, 9 critical)
Environment
All
Server
- Parse Server version:
NA - Operating system:
Mac OS v15.7.4 - Local or remote host (AWS, Azure, Google Cloud, Heroku, Digital Ocean, etc):
Local
Database
NA
Client
NA
Logs
➜ my-app git:(main) ✗ npm i
up to date, audited 879 packages in 3s
160 packages are looking for funding
run `npm fund` for details
50 vulnerabilities (6 low, 10 moderate, 25 high, 9 critical)
To address issues that do not require attention, run:
npm audit fix
To address all issues (including breaking changes), run:
npm audit fix --force
Run `npm audit` for details.
➜ my-app git:(main) ✗ npm list | grep parse-server
├── parse-server@4.10.20
node -v
v25.8.1
npm -v
11.11.0
Contributor guide
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.
Research direction
Start by reproducing the issue with npm i parse-server and inspect the installed version and the package metadata, including the package.json version range mentioned in the report. Trace how the published package resolves its default version; done means a fresh install selects the intended latest version within that range.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- release
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100