bug: align registry reachable logic with npm

[literat]

Hi,

this package is great and I want to use it but I am ending up on VPN. Because I have multiple registries behind company VPN.

And I also wonder. Classic publish configuration with one registry and without this package works just fine even the registry is behind VPN. But when I use this package and configure multiple publish registries I got information that are unreachable.

If I have ani clue where the problem might be I could try to modify it myself. So could you give me any advice, please?

Thank you.

[privatenumber]

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?

[literat]

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".

[privatenumber]

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.

[literat]

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.

[privatenumber]

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

[privatenumber]

Closed via #11