From c5719101cc08e3edf635bce0e365d5048458ca9a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Vegard=20=C3=98kland?= Date: Fri, 15 Jan 2021 20:50:33 +0100 Subject: [PATCH] docs: clarify node vs npm in FAQ (#1731) thanks @vegardok --- docs/support/FAQ.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/support/FAQ.md b/docs/support/FAQ.md index 180177a06c..451a5a4c46 100644 --- a/docs/support/FAQ.md +++ b/docs/support/FAQ.md @@ -8,7 +8,7 @@ By default, only the published package will contain the version, which is the on However, the [`@semantic-release/git`](https://github.com/semantic-release/git) plugin can be used to push the updated `package.json` as well as other files to the Git repository. -If you wish to only update the `package.json` and push via Git you can set the project to `"private": true,` within your `package.json` to prevent publishing to [npm](https://www.npmjs.com). This can be useful for using **semantic-release** with a non-node project. +If you wish to only update the `package.json` and push via Git you can set the project to `"private": true,` within your `package.json` to prevent publishing to [the npm registry](https://www.npmjs.com). ## How can I use a npm build script that requires the `package.json`’s version ?