Hello everyone
My environment：
Use nexus as the repository of npm, and nexus points to the official repository of npm.
My question:
When I install some dependencies using NPM, Most npm dependent packages can be downloaded normally.
However, some of them cannot be downloaded, and a 404 error is reported. At this time, I checked that the dependency package of this version did exist on the official website, and it was a new version that was updated a few hours ago, but this package was not synchronized in the nexus warehouse.
My npm package.json and package-lock.json does not specify the version of the dependent package, the default is the latest version.
It will look for the latest version of the dependency package by itself. At this time, the latest version of the dependency package exists in the official repository, but does not exist in the nexus repository.
So I think it should be a problem with the update mechanism of nexus to the proxy , but I can’t find where to configure it. Please help me.
Hi Smbands,
That sounds about right. Behaviour you described is due to caching NXRM performs in order to save your network bandwidth. It will re-check for latest version after caching time expires or you invalidate the cache. You can tweak how often NXRM will chcek for updated content in your upstream provider on your repository settings page. On the same page you can find a button to immediately invalidate the cache.
@dsawa
Thanks a lot for your answer.
I probably understand, and I know where to modify it according to your description.
“Invalidate cache” button
I think the next time this happens clicking on this button will invalidate the current cache and force it to reload the cache.Then I can get the latest version of the dependency package from the broker’s repository address.I’m looking forward to seeing this again so I can verify it.
