-
-
Notifications
You must be signed in to change notification settings - Fork 18
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
Comments
When generating, specify 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
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 thanhref="./_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 doingserve .
rather thanserve .eslint-config-inspector
.The text was updated successfully, but these errors were encountered: