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!
v2025 npm package not saved on server
-
Hi,
upon migrating to 2025 and using postgres we are encountering situations where npm is downloaded to the client but it is not saved on the proget server. we verified that the package can't be downloaded via anywhere else other then the proget itself. the last time it happened we deleted the npm feed, deleted the folder and recreated the feed.help is appreciated.
-
Hi @udi-moshe_0021,
I'm afraid we don't have enough information to help troubleshoot, but I'll try to explain how ProGet works behind the scenes.
If you have package caching enabled (the default), then packages downloaded through ProGet will be automatically cached. They will still show up with the "remote" icon, but they will be stored on the ProGet server. You'll be able to tell that they're cached (instead of remote) because there will be a "delete cached package" option.
You can verify this behavior by simply downloading a package from the ProGet UI. It will cache the package. The same link/url is used by the npm client to download a package file.
So why is a package not cached then? The most likely case is that the npm client already had it internally cached, and thus it was never requested from the server. You may also have a scenario where cached packages are deleted with a retention policy.
Thanks,
Alana -
@atripp HI,
i will try to clarify it a little bit.
we have a proget instance which is used as an intermediate server to download packages and move them to an air-gapped network. employees are invoking npm install in a terminal server and they are configured to use proget.
what we do not see is the package in the filesystem of the proget itself.hope i managed to clarify it
thanks,
udi -
Hi @udi-moshe_0021,
Thanks for clarifying.
In this case, then someone may have disabled package caching on the feed or deleted the package using the "clear cache" button, a retention policy, or manually. That is the most likely scenario here.
There may have also been an error adding the package to the feed (file system error, etc), although those are very rare and would have been logged under Admin > Diagnostic Center.
Thanks,
Alana -
@atripp Hi,
thank you very much.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login