From f9d414cebff972b5b0fae212e6f2938823752300 Mon Sep 17 00:00:00 2001 From: Roberto Basile Date: Sun, 25 Feb 2024 15:45:31 -0500 Subject: [PATCH] Update scope.md Missing = was causing error --- docs/lib/content/using-npm/scope.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/lib/content/using-npm/scope.md b/docs/lib/content/using-npm/scope.md index 829e6cc408e6c..b43fa2e9ff381 100644 --- a/docs/lib/content/using-npm/scope.md +++ b/docs/lib/content/using-npm/scope.md @@ -127,7 +127,7 @@ host multiple scopes, but a scope only ever points to one registry. You can also associate a scope with a registry using `npm config`: ```bash -npm config set @myco:registry http://reg.example.com +npm config set @myco:registry=http://reg.example.com ``` Once a scope is associated with a registry, any `npm install` for a package