From 49606f8fdfc45439e859678fd12bcbd8dc496b76 Mon Sep 17 00:00:00 2001
From: Rish <zrishabhgarg@gmail.com>
Date: Thu, 30 Apr 2020 17:37:29 +0530
Subject: [PATCH] Added explicit npm registry in publishConfig

no issue

The members-js package is published on npm and this ensures `yarn ship` attempts to push to correct registry instead of yarn registry in case not set globally.
---
 ghost/portal/package.json | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/ghost/portal/package.json b/ghost/portal/package.json
index 8694a96f13..213d55a1ca 100644
--- a/ghost/portal/package.json
+++ b/ghost/portal/package.json
@@ -11,7 +11,8 @@
     "README.md"
   ],
   "publishConfig": {
-    "access": "public"
+    "access": "public",
+    "registry": "https://registry.npmjs.org/"
   },
   "dependencies": {
     "@testing-library/jest-dom": "4.2.4",