docs: add Migrating from Node.js to Deno guide#3192
Merged
Conversation
crowlKats
approved these changes
Jun 8, 2026
… CommonJS/ESM resolution
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 "Migrating from Node" content lived as a couple of sections buried
inside the Node and npm compatibility page, and it opened with a list of
caveats that undersold Deno's actual drop-in compatibility — leading with
"expect little to no changes" and three things to watch out for.
This moves it into its own Migrating from Node.js to Deno guide and
rewrites the introduction to lead with the real expectation: most Node
projects run in Deno with no changes at all. The
node:prefix, explicitBufferimport, and CommonJS notes are demoted to the rare exceptionsthey are, framed as "if something doesn't run immediately" rather than
required migration steps.
The guide is extracted from node.md (which keeps a short pointer to it),
carries the migration and cheatsheet oldUrl redirects, fixes a few stale
links in the moved content, and updates the inbound link from the web
development page. A sidebar entry is added next to the Node page.
This branches from main and overlaps the runtime IA restructure in #3190
on _data.ts; once #3190 lands I will rebase this and move the sidebar
entry into the new Guides group.