Scan errors out with PROTOCOL_TIMEOUT

[Ryuno-Ki]

On Ubuntu in a corporate network
When I scan my employer's homepage (https://jambit.com/)
AND I turn DEBUG=* on,
Then I can see a start of the audit:

is-website-vulnerable/src/Audit.js

Lines 88 to 91 in 492bd53

	const scanResult = await lighthouse(url, opts, {
	extends: 'lighthouse:default',
	settings: this.settings
	})

And a timeout with PROTOCOL_TIMEOUT after a while (30 seconds?).

This does not happen when running the code
npx is-website-vulnerable https://jambit.com/ from home.

Looks like it were caused by GoogleChrome/lighthouse#6512 but this npm package might need to handle the error gracefully.

I haven't took time to clone the repo and run a local build.

[lirantal]

Thanks @Ryuno-Ki for the detailed report 👍
Indeed I think we just need to detect and gracefully handle with a descriptive error message

[rajkumaar23]

Can I take this up? @lirantal

[lirantal]

@rajkumaar23 definitely, thank you ❤️

[github-actions]

🎉 This issue has been resolved in version 1.14.4 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀