Cannot disable console warnings

[alioguzhan]

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

[alioguzhan]

I was able to get rid of the directAccess warning after a clean install and making sure it is being passed both in development and production modes.

The one about listening db events is still remaining. I believe it is being discussed in #7345 .

But I would still expect to have an option to silence all of these warnings regardless of the content or cause.

[mtrezza]

Thanks for reporting.

The warnings you listed are of level warn. It should be possible to set the log level to a higher level, for example error, to mute these warnings.