# NPM Group Repository Fetching Metadata from Second Proxy Despite Artifact Found in First Proxy (Nexus 3)

**URL:** <https://community.sonatype.com/t/npm-group-repository-fetching-metadata-from-second-proxy-despite-artifact-found-in-first-proxy-nexus-3/13568>\
**Category:** Sonatype Nexus Repository\
**Tags:** help, nexus-repository, maven, npm, group\
**Created:** [September 29, 2024, 2:10pm UTC](https://community.sonatype.com/t/npm-group-repository-fetching-metadata-from-second-proxy-despite-artifact-found-in-first-proxy-nexus-3/13568 "2024-09-29T14:10:58Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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:** [September 30, 2024, 2:52pm UTC](https://community.sonatype.com/t/npm-group-repository-fetching-metadata-from-second-proxy-despite-artifact-found-in-first-proxy-nexus-3/13568/2 "2024-09-30T14:52:03Z")

</div>

This is a duplicate of your previous post [Sonatype Nexus OSS 3.69.0 Npm Issue](http://community.sonatype.com/t/sonatype-nexus-oss-3-69-0-npm-issue/13419)

As I described previously it is expected that a group merges metadata from all group members. This is also the same behaviour as maven when a `maven-metadata.xml` file is requested.

---

_[View the full topic](https://community.sonatype.com/t/npm-group-repository-fetching-metadata-from-second-proxy-despite-artifact-found-in-first-proxy-nexus-3/13568)._