From 9eecdf162b7cbd8d750dfe9a35ad4eaa01850918 Mon Sep 17 00:00:00 2001 From: Rawal27 Date: Fri, 14 Aug 2026 12:30:29 +0530 Subject: [PATCH] docs: fix neither/nor usage Signed-off-by: Rawal27 --- content/cli/v10/configuring-npm/package-json.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/cli/v10/configuring-npm/package-json.mdx b/content/cli/v10/configuring-npm/package-json.mdx index 3d672bb4eee..a6272a6ac7c 100644 --- a/content/cli/v10/configuring-npm/package-json.mdx +++ b/content/cli/v10/configuring-npm/package-json.mdx @@ -544,7 +544,7 @@ Git URLs are of the form: `` is one of `git`, `git+ssh`, `git+http`, `git+https`, or `git+file`. -If `#` is provided, it will be used to clone exactly that commit. If the commit-ish has the format `#semver:`, `` can be any valid semver range or exact version, and npm will look for any tags or refs matching that range in the remote repository, much as it would for a registry dependency. If neither `#` or `#semver:` is specified, then the default branch is used. +If `#` is provided, it will be used to clone exactly that commit. If the commit-ish has the format `#semver:`, `` can be any valid semver range or exact version, and npm will look for any tags or refs matching that range in the remote repository, much as it would for a registry dependency. If neither `#` nor `#semver:` is specified, then the default branch is used. Examples: