Don't pollute stdout with warnings and errors

[everhardt]

Is your feature request related to a problem? Please describe.
No

Describe the solution you'd like
I'd love for node-opcua to not pollute stdout. I think dependencies should not do that (by default). Listening to messageLogger and deal with logs there seems to be a fine alternative. This requires:

1. A setting in the OPCUAClientOptions and the likes or process.env to enable writing to stdout. The setting should be adhered to in make_errorLog and make_warningLog.
2. No direct console.log calls, like:

   • node-opcua/packages/node-opcua-client/source/private/client_base_impl.ts

     Line 759 in 853d291

     console.log("Creating default certificate ... please wait");

   • https://github.com/node-opcua/node-opcua-crypto/blob/b00d552f91c43725717a7001c5054507d143a4b2/source/x509/_crypto.ts#L15 (even when only importing it and not using node-opcua at all!)

Additional context

N/A

[everhardt]

I'm open to making a PR along the lines of the desired solution if you agree to it.

[erossignon]

yes, please, use a warningLog

UPDATE; in fact, i am on it.

[everhardt]

Many thanks! Are you also open to the first part of my question:

1. A setting in the OPCUAClientOptions and the likes or process.env to enable writing to stdout. The setting should be adhered to in make_errorLog and make_warningLog.

I think the env variable is the easiest solution, I can make a PR for that if you like.

[erossignon]

@everhardt debugLog are now cleaned-up.

Sure, please add a mechanism to enable or disable warningLog and errorLog.
warningLog and errorLog should remain active by default, as it helps developers to troubleshoot common issues and highlight areas that requires attention during development phase.

[everhardt]

I'm sorry for my late reply, in the end I did not need to use this package anymore, so for now I won't be contributing.

[erossignon]

@everhardt thank you for joining the initiative, and thank your for you contribution to the code.
Let's close the issue for the time being as the bulk of the initial issue is solved.

[mb-software]

Since this has been closed as completed I assume it should now be possible to disable stdout output? If so, how to do it? I couldn't find it in the code. Is there an env variable to control the output?
Thanks

[GusakIurii]

Greetings.
I don't quite understand, is there a solution to disable WarningLog?
If so, can you provide a short example?