Skip to content

fix(core): serve static builds under a deploy path - #641

Draft
0froq wants to merge 1 commit into
vitejs:mainfrom
0froq:fix/583-static-deploy-base
Draft

0froq wants to merge 1 commit into
vitejs:mainfrom
0froq:fix/583-static-deploy-base

Conversation

@0froq

@0froq 0froq commented Nov 15, 2026

Copy link
Copy Markdown

Description

Pass Vite's base to buildHub as deployBase. Static snapshots now rebase frame bases, dock URLs, and the absolute asset references inside copied SPAs, so output served below the domain root works end to end. Bump @devframes/hub to , the first release with the option.

The option itself comes from devframes/devframe#494. Draft until that release is on npm.

Linked Issues

Fixes #583

Test

  • The reproduction from Static build: frame/panel URLs are still absolute when output is hosted at a subpath #583 with the hub fix applied locally: vite build --base /ci-build-123456/, then serve custom-dir at that path. The viewer, the rolldown panel, the messages and inspect panels, the _nuxt chunks, and the assets all return 200. A scan of the baked URLs finds no root-absolute leftovers.
  • No new automated test here. The rebasing lives in @devframes/hub and is covered by its build tests, and this PR forwards the option.

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

Successfully merging this pull request may close these issues.

Static build: frame/panel URLs are still absolute when output is hosted at a subpath

1 participant