You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 26, 2018. It is now read-only.
Networking is a bit of a hack right now, external ports have to exactly match internal ports for the system to work properly, due to how npm-delegate checks the npmjs instance and how it refers the client to downloading the package.
Allowing these ports to be more flexible would be nice. The best solution requires an upstream fix, but I think we can still be more flexible with our startup flags.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Networking is a bit of a hack right now, external ports have to exactly match internal ports for the system to work properly, due to how npm-delegate checks the npmjs instance and how it refers the client to downloading the package.
Allowing these ports to be more flexible would be nice. The best solution requires an upstream fix, but I think we can still be more flexible with our startup flags.
The text was updated successfully, but these errors were encountered: