bug: align registry reachable logic with npm about npm-multi-publish HOT 6 CLOSED

Ok, I have dive deeper into your code and check reachable of my urls using is-reachable.

https://nexus3-3.sandbox.cdev Ok
https://nexus3-3.sandbox.cdev/repository/npm-compres Fail
https://nexus3-3.sandbox.cdev/repository/npm-compres/ Ok

So, trailing slash 🤦

Thanks o lot for your help.

from npm-multi-publish.

Glad you were able to resolve it.

I will leave this open since I think there's room for improvement in this package to better align with how npm interacts with the registry.

Some references for me:

• npm ping
• npm publish
• npm-registry-fetch

from npm-multi-publish.

I don't quite understand the issue here, but npm-multi-publsih has support for registries behind VPNs. As a matter of fact, my personal use-case is to publish to multiple registries, each behind a different VPN.

Is it possible to upload a video of the problem you're encountering?
If you're getting an error, do you mind sharing it?

from npm-multi-publish.

We have 2 repositories, both using Nexus. Without this package publishing to first or second repository works just fine. Using this package I am stuck on "Retry" or "Exit".

from npm-multi-publish.

Maybe the prompt should be changed to "If it's behind a VPN, try enabling it" or something like that.

During that phase, make sure you're switching your VPN so https://nexus3-3.sandbox.cdev is reachable.

from npm-multi-publish.

Closed via #11

from npm-multi-publish.