New debug function spams console.logs when used with Jest

[wojtekmaj]

Steps to reproduce

Tell us about your environment:

• Puppeteer version: 5.0.0
• Platform / OS version: macOS Catalina
• URLs (if applicable): n/a
• Node.js version: 12.16.2

What steps will reproduce the problem?

When running Puppeteer via Jest (which provides global.document from JSDOM), isNode variable which new debug function uses improperly returns false.

What is the expected result?

Puppeteer remains relatively silent, not spamming with debug messages unless told to.

What happens instead?

Jest causes Puppeteer to spam the console with countless console.logs.

In fact, there are so many now that I've reached the limit of log length and my builds started crashing. This did not occur in v4.x.

I guess the core issue is that

• there is no way to stop the console.logs via any config, unlike in debug package where DEBUG env variable has to be provided for it to start logging debug stuff AND
• console.logs are used in Node environment if document variable is available