You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug report] Static builds can't be served under a subpath: baked URLs stay root-absolute #493
buildHub bakes absolute URLs for frame bases, dock entries, page scripts, and SPA asset references. When the built tree is served below the domain root, those URLs still point at /__..., so every panel and asset request 404s.
The deploy-root sibling layout from #355 works when the output is served at /.
Serve dist/ at /ci-build-123456/, for example with a static server mounted on that path. This is the layout Vite DevTools uses, where the hub sits at /__devtools/ and each integration SPA is a sibling.
Expected
/ci-build-123456/__panel/ loads, and its HTML references /ci-build-123456/__panel/....
Frame bases in __index.json and the dock snapshot in the RPC dump carry the same prefix.
The on-disk layout stays dist/__panel/ and dist/__devtools/.
Actual
Dock entries and frame bases bake /__panel/, so the iframe 404s.
A prebuilt SPA with root-absolute assets (/__panel/_nuxt/...) 404s for every asset even after the dock URL is fixed.
The RPC dump and __index.json keep the root-absolute strings.
Activity