# Nexus setup as npmjs.com proxy but missing latest versions of packages

**URL:** https://community.sonatype.com/t/nexus-setup-as-npmjs-com-proxy-but-missing-latest-versions-of-packages/9813
**Category:** Sonatype Nexus Repository
**Created:** [December 23, 2022, 2:32pm UTC](https://community.sonatype.com/t/nexus-setup-as-npmjs-com-proxy-but-missing-latest-versions-of-packages/9813 "2022-12-23T14:32:14Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![mark.perry](https://avatars.discourse-cdn.com/v4/letter/m/e9c0ed/32.png) [@mark.perry](https://community.sonatype.com/u/mark.perry)
#### Post date: [December 23, 2022, 2:32pm UTC](https://community.sonatype.com/t/nexus-setup-as-npmjs-com-proxy-but-missing-latest-versions-of-packages/9813/1 "2022-12-23T14:32:15Z")

</div>

Hi

When I request a package from our Nexus Proxy for something that I can find on [npmjs.com](http://npmjs.com) it is often the case that the latest version on [npmjs.com](http://npmjs.com) is 1-3 days old but that latest version is not present in my Nexus Proxy.

How does Nexus deal with updating versions of packages?

- Does it work on a timing basis?
- Am I able to force it update for a particular package and version?
- Does it recognise that I am asking for a package version that’s newer than the version already stored so it should then go and download it?

Currently I just get ECONNCT issues or 404 when asking Nexus for the latest verson.

Any help greatly received as this type of thing really slows down my development cadance.

Thanks, Mark

---

<div class="post-metadata">

### Author: ![mpiggott](https://avatars.discourse-cdn.com/v4/letter/m/f0a364/32.png) [@mpiggott](https://community.sonatype.com/u/mpiggott)
#### Post date: [January 4, 2023, 7:09pm UTC](https://community.sonatype.com/t/nexus-setup-as-npmjs-com-proxy-but-missing-latest-versions-of-packages/9813/2 "2023-01-04T19:09:52Z")

</div>

Nexus caches metadata for a period of time defined in your repository configuration.
