Closed
Description
New Issue Checklist
- I am not disclosing a vulnerability.
- I am not just asking a question.
- I have searched through existing issues.
- I can reproduce the issue with the latest version of Parse Server.
Issue Description
When updating #8558, I assumed the Node 14 failure was flaky. It was not.
The code uses String.replaceAll, which is available in Node 15+
Steps to reproduce
Actual Outcome
Expected Outcome
Environment
Server
- Parse Server version:
FILL_THIS_OUT
- Operating system:
FILL_THIS_OUT
- Local or remote host (AWS, Azure, Google Cloud, Heroku, Digital Ocean, etc):
FILL_THIS_OUT
Database
- System (MongoDB or Postgres):
FILL_THIS_OUT
- Database version:
FILL_THIS_OUT
- Local or remote host (MongoDB Atlas, mLab, AWS, Azure, Google Cloud, etc):
FILL_THIS_OUT
Client
- SDK (iOS, Android, JavaScript, PHP, Unity, etc):
FILL_THIS_OUT
- SDK version:
FILL_THIS_OUT