Attempt #n+1 to figure out what lerna's "lerna ERR! Only absolute URLs are supported" is about (and it not outputing a lerna-debug.out like it says it would...)

This commit is contained in:
Miel Truyen 2019-11-11 16:50:00 +01:00
parent 5415a390a9
commit 0febc4f55f
2 changed files with 5 additions and 2 deletions

View File

@ -192,7 +192,7 @@ new-version:
yarn lerna version --force-publish="@babel/runtime,@babel/runtime-corejs2,@babel/runtime-corejs3,@babel/standalone,@babel/preset-env-standalone" yarn lerna version --force-publish="@babel/runtime,@babel/runtime-corejs2,@babel/runtime-corejs3,@babel/standalone,@babel/preset-env-standalone"
publish-cerxes: prepublish publish-cerxes: prepublish
yarn lerna publish from-package --registry npm.cerxes.net --no-git-tag-version --no-push --no-git-reset --allow-branch initializer-fix --no-verify-access yarn lerna publish from-package --registry https://npm.cerxes.net --no-git-tag-version --no-push --no-git-reset --allow-branch initializer-fix --no-verify-access
# NOTE: Run make new-version first # NOTE: Run make new-version first
publish: prepublish publish: prepublish

View File

@ -33,5 +33,8 @@
"npmClient": "yarn", "npmClient": "yarn",
"npmClientArgs": [ "npmClientArgs": [
"--no-lockfile" "--no-lockfile"
] ],
"publishConfig": {
"registry": "https://npm.cerxes.net"
}
} }