Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Assets should be referenced with relative paths? #87

Open
mmkal opened this issue Sep 1, 2024 · 1 comment
Open

Assets should be referenced with relative paths? #87

mmkal opened this issue Sep 1, 2024 · 1 comment

Comments

@mmkal
Copy link
Contributor

mmkal commented Sep 1, 2024

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
Copy link
Contributor

voxpelli commented Sep 1, 2024

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

I agree that relative paths would be nice though

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants