From 614672b0a403b15d535b19341fd546bd023e263c Mon Sep 17 00:00:00 2001 From: Gar Date: Thu, 1 Jul 2021 09:02:54 -0700 Subject: [PATCH] fixup! fix(docs): clarify what install type gets .bins Co-authored-by: Jordan Harband --- docs/content/configuring-npm/package-json.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/configuring-npm/package-json.md b/docs/content/configuring-npm/package-json.md index 0ba8598dbd18b..b8a50c2637e8e 100644 --- a/docs/content/configuring-npm/package-json.md +++ b/docs/content/configuring-npm/package-json.md @@ -343,7 +343,7 @@ feature to install the "npm" executable.) To use this, supply a `bin` field in your package.json which is a map of command name to local file name. When this packaged is installed, npm will symlink that file into a place where it can be invoked by name if -installed globally, or by `npm exec` when installed in another package. +installed globally, or by `npm exec` or `npm run-script` when installed in another package. For example, myapp could have this: