Skip to content

docs: default to npm for unprefixed names in deno add/install (2.8)#3074

Open
lunadogbot wants to merge 1 commit intodenoland:mainfrom
lunadogbot:docs/2.8-default-npm-registry
Open

docs: default to npm for unprefixed names in deno add/install (2.8)#3074
lunadogbot wants to merge 1 commit intodenoland:mainfrom
lunadogbot:docs/2.8-default-npm-registry

Conversation

@lunadogbot
Copy link
Copy Markdown

Summary

Documents the behavior change in Deno 2.8 (denoland/deno#33246): deno add express and deno install express now resolve from the npm registry without needing npm: or --npm.

  • Updates runtime/reference/cli/add.md to describe the new default and how --jsr flips the default for unprefixed names.
  • Updates runtime/reference/cli/install.md similarly.
  • Notes that explicit npm: / jsr: prefixes still take precedence over the default.

Test plan

  • deno task serve — both pages render.

Updates the deno add and deno install reference pages to reflect the
2.8 behavior change: unprefixed names like \`express\` resolve to npm
by default, removing the need for \`--npm\` for the common case. Notes
that \`jsr:\` and \`npm:\` prefixes still take precedence and that
\`--jsr\` opts unprefixed names back to JSR resolution.

Refs denoland/deno#33246
@lunadogbot lunadogbot force-pushed the docs/2.8-default-npm-registry branch from 3e42e3e to bb10b87 Compare April 29, 2026 11:42
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