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
Static build: frame/panel URLs are still absolute when output is hosted at a subpath #583
After the fix, the root redirect and the DevTools SPA itself resolve correctly under a deploy base, but the URLs baked into the emitted manifests and RPC dumps are still root-absolute, so every sub-panel 404s.
Thanks for the reproduction, it made this easy to trace. The root cause is upstream in @devframes/hub: buildHub bakes root-absolute URLs for frame bases, dock entries, and page scripts, so the deploy path never reaches them. I opened devframes/devframe#494 to add a deployBase option for static builds.
The Vite side needs one line in buildStaticDevTools plus that hub release. There's a draft PR (#641) ready, and I'll mark it ready once the release is out.
Activity
0froq commentedon Nov 15, 2026
Thanks for the reproduction, it made this easy to trace. The root cause is upstream in
@devframes/hub:buildHubbakes root-absolute URLs for frame bases, dock entries, and page scripts, so the deploy path never reaches them. I opened devframes/devframe#494 to add adeployBaseoption for static builds.The Vite side needs one line in
buildStaticDevToolsplus that hub release. There's a draft PR (#641) ready, and I'll mark it ready once the release is out.