NEXUS-40286 - NPM group cache is not in sync with members

[jo-krk]

Hi,

We're using npm-group (Type: group, Format: npm) to group few repositories, one of them is npm-proxy (Type: proxy, Format: npm).

We noticed that npm-group cache is updated only during creation of the group (? not absolutely sure about this) and after clicking "Invalidate cache". However, there seems to be no later sync process between npm-proxy and npm-group , causing npm-group to always be outdated.

We were able to confirm that by checking json files provided for some selected package, e.g: example.com/repository/npm-group/%40angular-builders/jest example.com/repository/npm-proxy/%40angular-builders/jest

Available versions in those json files were different, but became the same after "Invalidating cache" on the npm-group. Invalidating cache on npm-proxy didn't triggered that though.

I believe we noticed this issue, for the first time, few years ago.

Nexus OSS version: 3.54.1-01 OS: Ubuntu Linux

Thank you.

[danischroeter]

We are experiencing a similar issue with an npm group repository. In our case there are multiple hosted npm repo (release and snapshot) that we access with a group repo. Randomly the group repo does not contain some versions and they are only availablle after using "Invalidate cache".

Interestingly the expected versions are shown correctly in the repo browser (nexus.xy/#browse/browse:npm:%40foo%2Fbar) but not in the repository (nexus.xy/repository/npm/%40foo/bar)

(We use Nexus 3.61.0)

[danischroeter]

This looks like the same issue: https://community.sonatype.com/t/npm-repository-group-not-updating-published-packages/9139