Search results

LHError: INVALID_URL

Status: Open.

#86 In GoogleChromeLabs/lighthousebot;

· bizmate opened on Mar 31, 2020

Error from CI backend. invalid json response body

Status: Open.

#76 In GoogleChromeLabs/lighthousebot;

· bronz3beard opened on Oct 15, 2019

GithubActions docs

Status: Open.

#72 In GoogleChromeLabs/lighthousebot;

· staabm opened on Sep 17, 2019

Provide option to set throttling?

Status: Open.

#66 In GoogleChromeLabs/lighthousebot;

· by12380 opened on Jul 1, 2019

Pass github error down to the client for debugging

Status: Open.

#64 In GoogleChromeLabs/lighthousebot;

· adamraider opened on Jun 16, 2019

npx alternative?

Status: Open.

#61 In GoogleChromeLabs/lighthousebot;

· kaihendry opened on May 12, 2019

Will lighthousebot supports the authenticated web pages?

Status: Open.

#60 In GoogleChromeLabs/lighthousebot;

· kabilan-ravi opened on Apr 10, 2019

Serverless frontend, backend and bot?

Status: Open.

#58 In GoogleChromeLabs/lighthousebot;

· iDVB opened on Mar 23, 2019

Returning performance 0 (error) every time

Status: Open.

#56 In GoogleChromeLabs/lighthousebot;

· balazsorban44 opened on Feb 19, 2019

Public-facing URL: needed?

Status: Open.

#52 In GoogleChromeLabs/lighthousebot;

· helloguille opened on Jan 28, 2019

Slack integration

Status: Open.

#50 In GoogleChromeLabs/lighthousebot;

· balazsorban44 opened on Jan 22, 2019

Error: no such file or directory, /home/chrome/reports/report.<hash>.json

Status: Open.

#49 In GoogleChromeLabs/lighthousebot;

· nolanlawson opened on Dec 9, 2018