This is not really a bug, nor a feature request, so I haven't followed any of the templates.

It seems console.error is being used in several situations, e.g.:

In most scenarios, these console.error calls are unnecessary as errors will be thrown anyway, that should be handled by devs consuming this library. In other situations, errors aren't thrown, and these messages are useful. However, most devs are using custom loggers (like JSON loggers), and would like to be able to customize the logging behavior.