-
Notifications
You must be signed in to change notification settings - Fork 9.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
--cli-flags-path
no longer works
#13589
Comments
This is actually any values from the flags json file 😱 This is what {
"budgets": [{"resourceSizes": [{"resourceType": "script", "budget": 1}]}],
"chromeFlags": "--lol"
}
The entire input of the file is spread into the object :P Strangest bit: the tests are just fine! |
connorjclark
changed the title
Jan 25, 2022
--cli-flags-path
no longer works for {budgets: [...]}
--cli-flags-path
no longer works
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Settings
budgets
will be undefined.I bisected to #13045. The PR doesn't update the
yargs
dependency, but did make some (seemingly trivial) modifications tolighthouse-cli/cli-flags.js
.Blocking GoogleChrome/lighthouse-ci#726
The text was updated successfully, but these errors were encountered: