jpnelson
commented
7 years ago In which part does the error occur? Presumably before publishing?
It's possibly a problem with one of our dependencies, so it'd be good to know exactly where this resolution is happening.
We're currently using a Lerna Multi Repo together with a local NPM Enterprise instance.
In this case the problem occured, that lerna-semantic-release resolved the npm repo url (correctly) to its IP address and posted all requests to this IP, but incorrectly used port 80 instead of port 8080.