Non-Comprehensive List of Things We Should Fix on Next Breaking Change .
_Update: everything open below is now represented in https://github.com/GoogleChrome/lighthouse/issues/5008_
auditContext?)scoreDisplayMode forces how it's displayed #4690 details real and good. #4616extendedInfometrics.js audit that contains all timings/timestamps in its details, so all the things don't need to reach into FMP.extInfodetails block, but should be. (here's what HA uses, what brendan uses)reportCategories ##4616displayValue and use details for it.audit.description -> audit.title, helpText -> description, name -> idtype: 'list' a tabletype: 'cards' a tablegeneratedTime -> fetchedAtfallbackKey/fallbackType for multi-typed columns (code snippets sometimes instead of URLs)?type:'metric' and type:'opportunity' as expressed in the LHR Lite docruntimeConfig to the report generating stageaudits: ['path/my-audit'] -> audits: { 'my-audit': {path: 'path/to/audit'}})Should we upgrade to node 8 as well?
@ebidel yup for sure, both these target #1999
we should remove chrome-launcher/. Kept only to preserve various places we suggested calling deep into our directory structure
#5008 has to be dealt with but this is a duplicate now
Most helpful comment
How about https://github.com/GoogleChrome/lighthouse/issues/1999