Some prior art here:

https://github.com/puppeteer/examples/blob/master/verify_sw_caching.js
https://michaljanaszek.com/blog/test-website-performance-with-puppeteer/#cacheAndServiceWorker

Would be nice if running pwmetrics in a non-tty environment suppressed ANSI code output.

Otherwise, output looks like:

Launching Chrome
  [32m✓[0m Success: [32mRun 1 of 3 finished successfully.[0m
Launching Chrome
  [32m✓[0m Success: [32mRun 2 of 3 finished successfully.[0m
Launching Chrome
  [32m✓[0m Success: [32mRun 3 of 3 finished successfully.[0m
        ☆  Median run  ☆

@Snugug shared a cool Github Actions pattern he's using to run multiple jobs in parallel but only after the project has been built. Basically it's a combo of the needs job property combined with uploading/downloading artifacts.

it gives two benefits:

1. you can do jobs in parallel, to get all

I missed the Chrome team adding "stack packs" in v5.0. Right now the only additional rules are for WordPress and AMP (and apparently React and Angular soon) but it would be cool to have a configuration flag to add these to the action.

https://github.com/GoogleChrome/lighthouse-stack-packs

Hi, thanks for this great tool!

lighthouse-ci doesn't explain why it failed

accessibility: 92
best-practices: 86
seo: 100
pwa: 77
Failed. ❌

Error: lighthouse-ci test failed.

It would be nice to output per line failed assertions, e.g. failed due to pwa < 80

This issue is a cross post of SO posted at: https://stackoverflow.com/questions/54307692/how-to-run-multiple-akka-net-lighthouse-seeds as there was no fix given by anybody. Essentially, Lighthouse documentation does not outline how to run multiple nodes or the best practices for that.

We can write docs anytime but we need to track what docs need to be done. These are in the form of markdown files in the docs directory. Some docs may be written but they are not audited for completeness, docs can always be more descriptive with examples.

• ci
  • circleci
  • travisci
• command
  • cra

Hello! First of all as the creator of lighthouse-gh-reporter id like to say that I'm so glad to see that my small tool contributed to inspire you. You put my idea to the next level as my next step in mind was exactly, more or less what you have done so.. congratulations 👍 👏

On the other hand I'd like to contribute into make this somet

Issue Overview

When requesting a report for a specific version of a plugin, if Tide doesn't yet have a report for it it'll start to generate one and return a <p>pending</p> response.

That response then gets cached, and will return the <p>pending</p> response until it expires.
Suffixing a ?1 to the URL to bypass the URL caching then results in being able to access it.

Steps to R