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.
2020-04-30 17:37:29 +05:30 · 2020-04-30 17:37:29 +05:30 · 49606f8fdf
commit 49606f8fdf
parent 02d968dd4e
1 changed files with 2 additions and 1 deletions
--- 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",