Assets should be referenced with relative paths?

[mmkal]

Hi! I'm testing a tool I'm building to upload CI artifacts to blob storage for browser viewing, and I've found the way config-inspector produces outputs makes it impossible to serve in a sub-directory of a storage service, I think because it uses absolute paths like href="/_nuxt/entry.DAgL5oUi.css" rather than href="./_nuxt/entry.DAgL5oUi.css".

Example: https://www.artifact.ci/artifact/blob/mmkal/artifact.ci/10656694828/eslint/.eslint-config-inspector/index.html (renders blank, this is mostly to show the URL structure I'm hoping to get working. Example of the same idea working for vitest: https://www.artifact.ci/artifact/blob/mmkal/artifact.ci/10656694828/vitest/vitest/html/index.html)

You can repro it by running npx @eslint/config-inspector build and then doing serve . rather than serve .eslint-config-inspector.

[voxpelli]

When generating, specify --base /your/path/ to make it possible to serve from a subdirectory

I agree that relative paths would be nice though