Closed Taewan-P closed 1 year ago
I don't know if this is related to the issue, but I use postgres for the db server.
Here is the diff that solved my problem:
diff --git a/node_modules/@lhci/server/dist/index.html b/node_modules/@lhci/server/dist/index.html
index 960e15e..6bffd00 100644
--- a/node_modules/@lhci/server/dist/index.html
+++ b/node_modules/@lhci/server/dist/index.html
@@ -21,7 +21,7 @@
l.href = url;
document.head.appendChild(l);
}
- loadStyle('chunks/entry-WKRDB3RZ.css');
+ loadStyle('/app/chunks/entry-WKRDB3RZ.css');
}());
</script>
</head>
Thank you for the information! 👍
This is fixed in https://github.com/GoogleChrome/lighthouse-ci/pull/879
Which was released in lhci v0.11.1
A matching new release of the patrickhulce/lhci-server
docker image also shipped yesterday.
And FYI we have a new release of lhci coming which bumps the LH version used to 10.x. You can watch #891 for updates on that.
Describe the bug A clear and concise description of what the bug is. Lighthouse Server UI starts to break when URL is not accessed from root URL.
To Reproduce Steps to reproduce the behavior:
Expected behavior A clear and concise description of what you expected to happen.
UI should not break at all circumstances
Logs/Screenshots If applicable, add LHCI logs or screenshots to help explain your problem.
However, when accessing to other pages after the ui is broken, there is a browser console error like this:
Server log shows all 200 in resources
Environment (please complete the following information):
Additional context Add any other context about the problem here.