Adam Raine
Adam Raine
Shoutout to @BioPhoton and https://github.com/push-based/user-flow for this idea. This allows the user to validate the user flow is performing the desired actions correctly before taking Lighthouse measurements. These speeds up...
Discovered here: https://github.com/GoogleChrome/lighthouse/pull/14130 That PR should fix the immediate problem, but our broken-links cron job didn't catch any broken links in the changelog: https://github.com/GoogleChrome/lighthouse/blob/47c318504425e1955a1c7cf7954a837bbed424ae/.github/workflows/cron-weekly.yml#L8-L26
In https://github.com/GoogleChrome/lighthouse/issues/14048, we are going to expose the FR api on the default node entry point. Any breaking changes to the FR API should be done in a breaking release...
This change prevents the plugin from operating in "timespan" and "snapshot" modes which can be used to audit a page beyond the initial page load: https://github.com/GoogleChrome/lighthouse/blob/master/docs/user-flows.md. The "navigation" mode is...
`oopif-requests` has been failing a lot recently, I believe it has something to do with the upgrade to Puppeteer 16. It was failing how it usually does, with missing network...
Proposal that closes https://github.com/GoogleChrome/lighthouse/issues/14396 See my comments for #14396 for the reasoning.
Follow up to #14341. There is still a `core/test/fixtures/fraggle-rock` directory but that can be updated in a future non-breaking release.
Closes #14049 - Only one config can be used for the entire user flow. Individual steps can specify settings overrides via the step flags but cannot use an entirely different...
Moving this discussion from https://github.com/GoogleChrome/lighthouse/pull/14329#issuecomment-1230846765. I could go either way but maybe `s` makes more sense to be consistent with older versions of LH.