parse-community / parse-community/parse-server
Replace outdated http request dependency with Node 18's `fetch`
Nobody has claimed this yet.
- #8282 by @dblythy — closed without merging
- Dominant language
- JavaScript
- Stars
- 21.4k
- Forks
- 4.8k
- Avg merge
- 7h 45m
- Merged PRs (30d)
- 11
Description
New Feature / Enhancement Checklist
- I am not disclosing a vulnerability.
- I am not just asking a question.
- I have searched through existing issues.
Current Limitation
Our docs state:
You can use your favorite npm module to make HTTP requests, such as request. Parse Server also supports Parse.Cloud.httpRequest for legacy reasons
Why should we continue to support a legacy HTTP module, which hasn't been updated in 3 years, where there are more popular solutions that constantly update their security issues and vulnerabilities?
The http module also uses deprecated methods, such as querystring and parse.
Also request is archived, so we shouldn't recommend that either.
We've seen Parse.Cloud.httpRequest be the source of many issues
Feature / Enhancement Description
Migrate to a dedicated HTTP library, such as axios
Example Use Case
Log Parse.Cloud.httpRequest is depreciated. Please migrate to different HTTP request solution
Alternatives / Workarounds
- Keep the legacy library as is.
- Set Parse.Cloud.httpRequest as an alias to
axios.
3rd Party References
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 tracing the Parse.Cloud.httpRequest entry point and locating its current legacy HTTP dependency. Resolve whether the intended replacement is Node 18's fetch or axios, then identify the relevant request tests and documentation references. Done should include the migration, updated guidance, and the proposed deprecation log without breaking existing HTTP request behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- api, backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100