Repository navigation
Move Playground hosting to Vercel - #111
Merged
Merged
Conversation
- sent from alixander's Codex
- sent from alixander's Codex
alixander
marked this pull request as ready for review
October 5, 2026 00:02
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Human
AI
Move the public D2 Playground to Vercel for production and pull request previews. Both
play.d2lang.comandplayground.d2lang.comserve the static build; preserve the existing Plausible script and event proxies. Remove the AWS deployment workflow and script so future production updates have a single deployment path.The build pins Yarn 1.22.22 and esbuild 0.16.3, checks out the public editor submodules, and emits ordinary assets in
distso Vercel can apply HTTP compression. Assets retain their existing URLs and revalidate on subsequent visits. Add the Vercel Open Source Program README badge and production/rollback instructions.Validation: the exact branch head deployed successfully on Vercel with Node 24; browser checks rendered Dagre, ELK, and TALA diagrams, restored a shared URL, and downloaded a valid SVG. JavaScript and CSS return Brotli encoding, the editor WASM loads, and the Plausible script proxy responds successfully. Both custom domains have valid Vercel TLS certificates prepared before DNS cutover. GitHub
ciandnofixupschecks passed, andgit diff --checkpassed.The companion infrastructure change adopts both Vercel DNS records and disables only the dedicated Playground CloudFront distribution while retaining the versioned S3 origin and shared certificate for rollback.