Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.
If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!
Remote package
-
I am testing ProGet for offline system.
So, I have Internet facing ProGet with npm connector to npmjs.org and offline server.
I tried npm install with some package.json file on server with access to Internet. When I check .npm folder on the server I did't find some packages. I checked on the feed and they appear as Remote packages.
I can go to specific package version and "Pull to ProGet", then it will appear on file systems as well.
Why it happens? And how can I be sure that all packages are downloaded locally?
Thank you in advance!
-
I'm afraid we don't have enough information to troubleshoot the problem. The use case you describe (using ProGet as an offline cache) is very common, so it might be some kind of misconfiguration on the npm side or something. I don't realy know.
I would check the npm logs, try to monitor http traffic, etc.
If you can "see" the package in ProGet as a Remote Package, and then download the package from the web page, then the npm client can do the same. The npm API cannot "see" whether it's a local, cached, or remote package, so the package is pulled regardless.
Best,
Alana
