Respect --silent flag

Hey there, thanks a lot for the beautiful tool! Can you please improve the warning about outdated caniuse-lite version? At the moment it doesn’t respect --silent flag and print messages in the console: https://github.com/browserslist/browserslist/blob/4db22aed0f0453b73fabc87264bf7210d101075b/node.js#L373-L378

https://docs.npmjs.com/misc/config#loglevel

[ai]

Why do you think this warning is not important for your case?

[extronics]

Why do you think this warning is not important for your case?

I’m on a typescript/backend project using jest for tests. Since typescript + jest may use babel for transpilation (https://jestjs.io/docs/getting-started#using-typescript) which in turn uses @babel/preset-env, i’m now getting browserslist included in a backend-only project. So these warnings don’t do anything for me (except maybe annoying me) since the code is not built for browsers.

I assume backend+typescript+jest it not that rare of a stack so there are probably a lot of users out there with this issue.

It would be great if you could accept that your views on good practices may not hold for 100% of all cases where this library ends up in the dependencies. It’s questionable behaviour already for a library somewhere deep down the dependency tree to start printing to the current process’ standard error. Just imagine ANY non-human interpretation of process output suddenly receiving random outputs from libraries. So at least consider providing an escape hatch to silence this.