docs: add migrate-from npm, pnpm, and Yarn pages#3285
Open
bartlomieju wants to merge 2 commits into
Open
Conversation
Replace the unified switch_package_manager guide with the per-tool npm, pnpm, and Yarn pages: redirect its URL to the npm page, carry over the fuller command mapping (audit, why, ci, dev dependencies) and the node_modules layout note, and rewire the sidebar. Also fix the deno.lock anchor and point the Node guide at the per-tool pages.
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
1 participant
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 is meant to cover moving to Deno from anywhere, and
people switching from a specific package manager search for that tool by
name. Until now that audience was served by a single unified guide,
switch_package_manager, which is one URL competing for "migrate from npm",
"migrate from pnpm", and "migrate from yarn" at once. This splits it into a
dedicated page per package manager so each one can own its search term and
its tool-specific advice.
Each page leads with the same honest framing, that a package manager is
configuration rather than code, so Deno reads the existing package.json and
most projects run unchanged, then carries the command cheatsheet and the
parts specific to that tool. npm and Yarn workspaces live in package.json
and are read directly, so there is nothing to convert; the pnpm page
documents converting pnpm-workspace.yaml (packages and catalogs) into
deno.json by hand. The Yarn page covers Plug'n'Play, which Deno does not
implement. The npm page also carries the incremental-adoption framing (use
Deno as your package manager while still running the app with Node) and
absorbs the redirect from the old unified URL.
The previous switch_package_manager guide is removed and its URL redirects
to the npm page; its fuller command mapping (audit, why, ci, dev
dependencies) and the node_modules layout note are folded into the per-tool
pages, and the sidebar now lists the three pages in its place. The pages are
written against currently shipped behavior only, so they stay correct
regardless of in-flight runtime changes, and every command and config field
was verified against the CLI reference or by running Deno.