core(config): add category weight to perf config #3529
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I noticed that when running the Lighthouse with the
--perf
flag, the top levelscore
value in the generated json report is0
even when thescore
of theperformance
category is higher than0
. I expected these values to be the same whenperformance
is the only category being evaluated.This pull request simply adds default weights to
performance
,accessibility
, andbest-practices
.pwa
already had a weight.Here's one way I tested this change.
I encountered this problem when I was walking through https://github.com/ebidel/lighthouse-ci from @ebidel which relies on the top level
score
value of the json report generated by lighthouse.