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.

Write HTML reports to .lighthouseci folder during collect

See original GitHub issue

I’m attempting to replace a custom lighthouse test configuration with lhci. I’m not getting HTML output in .lighthouseci, only json. I’ve attempted to define the lighthouse settings in lighthouserc.json:

{
  "ci": {
    "collect": {
      "settings": {
        "output": ["html"],
        "skipAudits": ["is-cralwable"],
        "useThrottling": "true",
        "onlyCategories": [
            "performance",
            "accessibility",
            "best-practices",
            "seo"
        ]
    },

...

And also pointing to the original configuration file:

{
  "ci": {
    "collect": {
      "settings": {
        "configPath": "./tests/lighthouse/lighthouse-config.js"
    },

...

with lighthouse-config.js containing:

module.exports = {
    extends: 'lighthouse:default',
    settings: {
        output: ['html'],
        skipAudits: ['is-cralwable'],
        useThrottling: true,
        onlyCategories: [
            'performance',
            'accessibility',
            'best-practices',
            'seo'
        ],
    },
}

Does LHCI not allow for HTML result pages, or am I doing something wrong?

Issue Analytics

State:
Created 4 years ago
Comments:7

Top GitHub Comments

1reaction

patrickhulcecommented, Dec 4, 2019

It was just a proposal, we’ll just write the HTML reports to .lighthouseci for now unless there becomes more demand for a filesystem target.

0reactions

alexfornutocommented, Dec 4, 2019

Is filesystem currently a valid target for upload, or are you suggesting that as a solution? The docs don’t indicate it as an option currently.

I agree that writing HTML reports into .lighthouseci is good enough for me. If you wanted to implement filesystem as a target for upload, a possible advantage would be defining a target artifact directory, instead of having to move/point from/to .lighthouseci in the CI system config. Up to you if that’s worth the effort.

Thanks for your attention to this issue!