Skip to content

build(www): deploy the hosted editor from this repo on Vercel - #42

Open
DavidBabinec wants to merge 1 commit into
mainfrom
build/www-vercel-deploy
Open

DavidBabinec wants to merge 1 commit into
mainfrom
build/www-vercel-deploy

Conversation

@DavidBabinec

Copy link
Copy Markdown
Contributor

coreframework.com/app is stuck on 1.10.4. It embeds the editor from alpha.coreframework.com, which is the Vercel project core-bunch/core-framework. That project is still connected to the old private repo (its last production deploy is 80abe2ce, "Release: 1.10.4"). This adds packages/www/vercel.json so the project can build www from this repo with Root Directory packages/www, using Bun 1.3.11 via bunx as Vercel's docs recommend for pinning. It also documents the web app's release path in RELEASING.md, the README and the release skill: repo, branch, project, and that a merge to main deploys.

No SPA rewrite: the editor has no client-side routes, and a catch-all would serve index.html for a missing chunk instead of a 404. The Vercel dashboard switch is still a manual step, done separately.

Verification

# clean worktree, from packages/www, commands read from vercel.json
bunx bun@1.3.11 install --frozen-lockfile   # exit 0, bun v1.3.11, 3690 packages
bunx bun@1.3.11 run build                   # exit 0, dist/ bundle contains "2.0.2", no x-api-key or picsum.photos

Served that dist inside an iframe host mirroring the website: it loaded a project saved by live 1.10.4 and completed a save round-trip.

coreframework.com/app embeds the editor from alpha.coreframework.com,
whose Vercel project was still connected to the old private repo and
served 1.10.4. This adds the build settings Vercel needs to build www
from packages/www in this monorepo, pinned to the repo's Bun 1.3.11,
and documents that a merge to main is the web app's release.

No SPA rewrite: the editor has no client-side routes, and a catch-all
would answer a missing asset with index.html instead of a 404.

This branch has not been deployed

No deployments
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.

1 participant