Problem when urls as dependency in package.json?

[Way]

I recently ran into an issue where I used an url instead of a version for a dependency. That dependency was not resolved correctly and the package was missing.
Is there any known problem with this case?

[vladikoff]

@Way you need to make sure that the box that is running the server is properly configured to resolve those urls. You can do a simple test on that deployed freight server and try to install something manually with npm to check if that works.