Skip to content
coders.talk
PirefactorWeb6 files · +43 −34

Switch pi-web release pipeline from Vue to Svelte package

Session from pi-web on Hugging Face by woxQAQ · MIT · condensed by Coders Talk

3msession
0interventions
by library · 1d
pnpmViteSvelteVueTypeScriptGitHub Actions
GOAL

Move the main release/build pipeline of the pi-web monorepo from the Vue client (packages/web) to the new Svelte 5 client (packages/svelte), keeping Vue as a legacy fallback.

  1. Prompt · +0
    Move the release main line to packages/svelte/
  2. Agent did · +0m
    Explored monorepo structure: read package.json, pnpm-workspace.yaml, package.json files for svelte/web/bin/bridge, README, AGENTS.md, CI/release/pi-install workflows, and vite configs to understand current Vue-based build pipeline.
  3. Agent did · +1m
    Tried to patch package.json with apply_patch (missing binary, failed), then used the edit tool instead to update build/dev scripts so build:web and dev:web point to the Svelte package, adding legacy build:vue/dev:vue aliases for the old Vue client.
  4. Agent did · +1m
    Updated AGENTS.md, README.md, and the CI/release/pi-install GitHub workflow files to describe Svelte as the current release main line and Vue as legacy, without changing the underlying build:web command they call.
  5. Agent did · +2m
    Ran `pnpm run build` to verify the new pipeline builds the server and the Svelte web bundle successfully end to end.
  6. Agent did · +2m
    Reviewed git diffs across package.json, AGENTS.md, README.md, and the three workflow files, and re-checked the final script names (build:svelte, build:vue, build:web, dev:* variants) to confirm the switch was consistent.
  7. Outcome · +3m
    Release pipeline switched: build:web/dev:web now point to packages/svelte, legacy build:vue/dev:vue kept for packages/web, docs (AGENTS.md, README) and CI/release/pi-install workflow step names updated, and `pnpm run build` passes producing the Svelte web-dist.
VERDICT

Next time I'd tell the agent upfront that Vue should become a legacy alias rather than be removed, so it doesn't have to reverse-engineer that from the workflows. The fix that actually did the work was switching from the broken apply_patch call to the built-in edit tool for package.json — after that the rest of the doc and workflow updates went smoothly, and `pnpm run build` confirmed the new Svelte pipeline actually works.

I tried this · 0

Discussion · 0

How Builds work