Feature request: add option to make unlighthouse-cli build-static assets have a relative path and use <base> tag about unlighthouse

[harlan-zw]

Hey @bux

Thanks for taking the time to make an issue.

What exactly is the issue with routerPrefix? I had created that configuration initially to solve this exact issue, as some integrations run from /__unlighthouse/.

[bux]

hi @harlan-zw

i'm using this config for unlighthouse-ci with --build-static

export default {
  site: "vite-starter-template.netlify.app",
  outputPath: "2022-04-07",
  routerPrefix: "lhk/2022-04-07",

  scanner: {
    device: "mobile",
    throttle: true,
  },
};

The results folder is being output to the subfolder lhk of the root project dir.
When running a node HTTP server (serve) from the root project dir and navigating to the the subfolder lhk/2022-04-07 I can see some part of unlighthouse, but some assets fail to load and screenshots and reports don't seem to use the routerPrefix:

[harlan-zw]

Hey @bux

This should be sorted in version 0.3.20. Let me know if you have any other issues :)

npx [email protected] --config-file <your-config> --build-static

[bux]

Awesome. I will take a look into it. Thanks

[bux]

@harlan-zw

unlighthouse/0.3.21 win32-x64 node-v16.14.0

Does unlighthouse keep a build cache somewhere?
The index.[].js that is created contains an older prefix:

[bux]

@harlan-zw do you know what is happening here?