-
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
Make it easier to run a specific audit category from CLI #4478
Comments
love it, this would be fixed by the broader effort to unify the config and CLI settings which I've got a branch in progress to do :) it would look like
|
@patrickhulce just checking, what's the status of your "broader effort"? Is this issue obsolete yet? |
Hi 👋🏻 I was trying the flag ligthouse http://google.com --only-categories=performance,pwa,best-practices but instead, it seems you support a much more tedious one: ligthouse http://google.com --only-categories=performance --only-categories=pwa --only-categories=best-practices Is there any scope/interest to change this? I would be happy to help with the change 🙋🏻♂️ 👨🏻💻 😊 |
@lluia This is a built-in feature of yargs that does the repeated categories that way. How about you file an issue with the feature request for discussion, but I think we'd love your help :) |
My use case is to run only the SEO audits from the LH CLI. Disabling non-SEO audits would help speed up the test. Additionally, disabling irrelevant things like network throttling could help with audit performance.
Strawman proposal:
--audit_categories=seo
,--audit_categories=seo,perf
cc @kdzwinel
The text was updated successfully, but these errors were encountered: