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.
This commit is contained in:
parent
02d968dd4e
commit
49606f8fdf
@ -11,7 +11,8 @@
|
|||||||
"README.md"
|
"README.md"
|
||||||
],
|
],
|
||||||
"publishConfig": {
|
"publishConfig": {
|
||||||
"access": "public"
|
"access": "public",
|
||||||
|
"registry": "https://registry.npmjs.org/"
|
||||||
},
|
},
|
||||||
"dependencies": {
|
"dependencies": {
|
||||||
"@testing-library/jest-dom": "4.2.4",
|
"@testing-library/jest-dom": "4.2.4",
|
||||||
|
Loading…
Reference in New Issue
Block a user