From e3de7befb3a9e2fcb7aac5b740d09b3b7d99d724 Mon Sep 17 00:00:00 2001 From: Darcy Clarke Date: Fri, 12 Feb 2021 13:33:52 -0500 Subject: [PATCH] docs(readme): add note back about branding/origin PR-URL: https://github.com/npm/cli/pull/2685 Credit: @darcyclarke Close: #2685 Reviewed-by: @isaacs, @lumaxis, @ljharb --- README.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/README.md b/README.md index 3b6b30513db5d..387443ed7611b 100644 --- a/README.md +++ b/README.md @@ -51,3 +51,13 @@ npm * `npm` is configured to use the **npm Public Registry** at [https://registry.npmjs.org](https://registry.npmjs.org) by default; Usage of this registry is subject to **Terms of Use** available at [https://npmjs.com/policies/terms](https://npmjs.com/policies/terms) * You can configure `npm` to use any other compatible registry you prefer. You can read more about configuring third-party registries [here](https://docs.npmjs.com/cli/v7/using-npm/registry) + +### FAQ on Branding + +#### Is it "npm" or "NPM" or "Npm"? + +**`npm`** should never be capitalized unless it is being displayed in a location that is customarily all-capitals (ex. titles on `man` pages). + +#### Is "npm" an acronym for "Node Package Manager"? + +Contrary to popular belief, **`npm`** **is not** in fact an acronym for "Node Package Manager"; It is a recursive bacronymic abbreviation for **"npm is not an acronym"** (if the project was named "ninaa", then it would be an acronym). The precursor to **`npm`** was actually a bash utility named **"pm"**, which was the shortform name of **"pkgmakeinst"** - a bash function that installed various things on various platforms. If **`npm`** were to ever have been considered an acronym, it would be as "node pm" or, potentially "new pm".