Configurable server listen time for startServerCommand

My app is SSR, and I’ve tried to use “LHCI autorun” but Lighthouse fails to run the correct files (since it seems to run whatever is in a “./dist” or “./public” folder).

I’m trying the complex setup guide now, and ran into using a shell script. My current script looks something like this :

#!/bin/bash

# ... (build condition check)

# ... (server setup)

# Install Lighthouse CI
# If you're already using node to manage your project, add it to your package.json `devDependencies` instead to skip this step.
npm install -g @lhci/cli@0.3.x

# Run a healthcheck to make sure everything looks good before we run collection.
lhci healthcheck --fatal

# Collect Lighthouse reports for our URL.
lhci collect --url=https://google.com --settings.chromeFlags=--no-sandbox \
    lhci upload target=temporary-public-storage \
    || echo "LHCI script failed!" \

# Assert that the reports look good, this command can be configured to ease your Lighthouse transition.
lhci assert --preset="lighthouse:recommended"
EXIT_CODE=$?

# ... (kill server)

exit $EXIT_CODE 

However, on CircleCI when it runs the script, it seems to run the tests on a different port (rather than testing at my url “https://google.com”).

Please advise on how to proceed if I want to be testing staging envs, thanks!

[patrickhulce]

Thanks! Let’s focus on the autorun issue because that should definitely be working.

When you were running lhci autorun did you have collect look like the below with url as an array? (Also try changing numberOfRuns to 1 to make sure the configuration is being picked up at all)

{
  "ci": {
    "collect": {
      "numberOfRuns": 1,
      "url": ["https://www.google.com"]
    },
    "assert": {
      "preset": "lighthouse:recommended",
      "assertions": {
        "offscreen-images": "off",
        "uses-webp-images": "off"
      }
    },
    "upload": {
      "target": "temporary-public-storage"
    }
  }
}

[Tonyhliu]

Thanks for your help @patrickhulce !