docs: add a Migrating from Bun guide#3235
Open
bartlomieju wants to merge 1 commit into
Open
Conversation
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.
The migrate section's direction is "migrating TO Deno from anywhere", but it
only covered Node. This adds /runtime/migrate/migrate_from_bun/ for the Bun
audience: run an existing project (leading with the permission-prompt
difference, the one thing Bun users won't expect), a verified command
cheatsheet, API equivalents for the big surfaces (Bun.serve to Deno.serve,
bun:sqlite to node:sqlite, Bun.file, bun:test, Bun.$), and an honest section
on what has no direct equivalent (macros, HTMLRewriter).
Every disputed fact was checked rather than assumed: node:sqlite confirmed
by importing it, HTMLRewriter confirmed absent the same way, deno bundle
footnoted as experimental per its own page, Bun-side claims verified against
bun.com/docs, and bunx maps to deno x (per our own CLI reference) rather
than a deno run incantation. The page is deliberately not yet linked from
the migrate hub or sidebar; that wiring lands with tomorrow's sidebar
regroup to avoid conflicting with the PRs already in flight.