Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Document --no-enable-error-reporting and CI env var
See original GitHub issuehttps://github.com/GoogleChrome/lighthouse/blob/master/docs/error-reporting.md mentions the --no-enable-error-reporting but the readme and lighthouse --help do not list this flag.
That page also mentions as CI env variable. Needs examples and mention of that in --help.
It may also be better to rename the flag --disable-enable-error-reporting to be consistent with the other disable flags.
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Codeigniter displays a blank page instead of error messages
Is there any way to show PHP error messages instead? It's very hard to debug when I get no feedback. My environment is...
Read more >Handling Multiple Environments - CodeIgniter
The simplest method to set the variable is in your .env file. ... Conversely, setting the constant to production will disable all error...
Read more >GitLab CI/CD variables
Documentation for GitLab Community Edition, GitLab Enterprise Edition, Omnibus GitLab, and GitLab Runner.
Read more >Introduction to environment variables - CircleCI
Secrets masking is not available on version 2.x of self-hosted installations of CircleCI server. Environment variables and contexts may hold project secrets or ......
Read more >PHP error reporting - WordPress VIP Documentation
A php.ini configuration file sets a default for all PHP error reporting to be enabled for a WordPress environment except for notices, ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Oh that’s nice. I guess there’s no way for someone to know that…we’re using yargs.
should we create a new issue to remove all disable cli options and move to --no-… when we reach a new major?
We can for now start supporting both but only mention --no in help