This behavior seems dangerous to me. If there is an important error but the logger has been configured incorrectly, the error will never get to Sentry, so you might just think that your code never throws any errors (unless you are comprehensively checking the logs).

What do you think about sending the error to Sentry but replacing the logger argument with a message like "sentry-node was incorrectly passed a non-string logger". Then anyone looking at the Sentry error will know to fix it. Alternatively we could just `JSON.stringify` the logger argument and leave it to the user to decide if they want to change it.