From e83e5c9bad93e598969088ae780149dbe34c6b5c Mon Sep 17 00:00:00 2001 From: Gar Date: Tue, 22 Feb 2022 11:47:56 -0800 Subject: [PATCH] docs: clarify npm init @latest behavior (#4435) Closes: https://github.com/npm/cli/issues/3821 --- docs/content/commands/npm-init.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/docs/content/commands/npm-init.md b/docs/content/commands/npm-init.md index a608061a96d8d..e9212a37e0f25 100644 --- a/docs/content/commands/npm-init.md +++ b/docs/content/commands/npm-init.md @@ -38,6 +38,15 @@ strictly additive, so it will keep any fields and values that were already set. You can also use `-y`/`--yes` to skip the questionnaire altogether. If you pass `--scope`, it will create a scoped package. +*Note:* if a user already has the `create-` package +globally installed, that will be what `npm init` uses. If you want npm +to use the latest version, or another specific version you must specify +it: + +* `npm init foo@latest` # fetches and runs the latest `create-foo` from + the registry +* `npm init foo@1.2.3` # runs `create-foo@1.2.3` specifically + #### Forwarding additional options Any additional options will be passed directly to the command, so `npm init