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.
Proposal: use PageSpeed Insights API to collect results
See original GitHub issueProblem: It’s hard to ensure consistent performance results. Burstable or uncontrollable CI VMs, like Github Actions https://github.com/treosh/lighthouse-ci-action/issues/14, may lead to inaccurate results. It significantly reduces the value of CI testing, since results can’t be trusted.
Proposal: using a dedicated Lighthouse as a Service API, like PSI, may help to provide consistent results and improve the collection time:
yarn lhci collect --psiToken=secret-token --numberOfParallelRuns=5
Trade-off: it doesn’t support any custom features or configs, and local testing is not possible. So it’s only for public-facing URLs.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:9
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
this was fixed by #340 🎉
@patrickhulce I’d be more than happy in sharing our details for that doc!