After publishing a new version into a NPM hosted repository, the NPM group repository, which has this NPM hosted as a member, does not show this newly published version in this component's metadata JSON file.
Use [ Invalidate cache ] button from the group repository page.
If above doesn't work, delete the metadata json from the group repository (eg: with a groovy script), so that next request will rebuild this metadata.
See internal comments for an artificial way of reproducing this behaviour.
- Nexus should make sure that rebuilding the metadata for necessary NPM group repositories is successful.
- It is very challenging to troubleshoot when this issue happens, so adding more logging would be helpful.
For example, current theory is somehow Nexus might not be invalidating the npm cache in com.sonatype.nexus.repository.npm.internal.orient.OrientNpmGroupDataFacet#on, so it would be helpful if we had some logging when matchingEvent(updated) = true but hasBlobBeenUpdated(updated) = false with some reason.