parse-community / parse-community/parse-server
Cannot disable console warnings
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 21.4k
- Forks
- 4.8k
- Avg merge
- 7h 45m
- Merged PRs (30d)
- 11
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
I have below log appears when I started the Parse server:
warn: DeprecationWarning: The Parse Server option 'directAccess' default will change to 'true' in a future version. Additionally, the environment variable 'PARSE_SERVER_ENABLE_EXPERIMENTAL_DIRECT_ACCESS' will be deprecated and renamed to 'PARSE_SERVER_DIRECT_ACCESS' in a future version; it is currently possible to use either one.
DeprecationWarning: Listening to events on the Db class has been deprecated and will be removed in the next major version.
And this warning causes pm2-dev to keeps restarting the process. I want to disable this warning in development mode so I tried below in server options:
{
verbose: false,
silent: false,
logLevel: "error"
}
I also tried to set directAccess explicitly in server options but not luck. It is still there.
Steps to reproduce
Install the parse-server from master branch.
Actual Outcome
I can't disable / silence the warnings.
Server
- Parse Server version:
git+https://github.com/parse-community/parse-server.git#f6a4172 - Operating system:
Ubuntu 20.04 - Local or remote host (AWS, Azure, Google Cloud, Heroku, Digital Ocean, etc):
localhost
Database
- System (MongoDB or Postgres):
Mongo - Database version:
4.4.4 - Local or remote host (MongoDB Atlas, mLab, AWS, Azure, Google Cloud, etc):
localhost
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 warning output from Parse Server on the master branch with the reported server options and pm2-dev setup. Trace where the two deprecation warnings are emitted and determine the existing configuration or logging path involved; done means development can suppress these warnings without triggering pm2-dev restarts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100