What is wrong with the NPM repository? - Sonatype Nexus Repository - Sonatype Community

What is wrong with the NPM repository?

post by roland.asmann on Sep 18, 2025

I’ve been setting up and testing a bit with NPM repositories and have now had my cleanup policies run. By my rules, the repo should currently be empty, but for some reason I see this in the repo:

When selecting these entries, I get the option to ‘Delete asset’, although I believe these should all be folders when filled…
What are these entries and why are they here? And more importantly, do they count toward my component/asset limit, even though in actuality nothing is there?

post by mpiggott on Sep 18, 2025

Those files would be metadata shared across versions, these aren’t currently covered by cleanup.

post by roland.asmann on Sep 19, 2025

OK, but what about my second question? Do they or do they not count toward the component limit?

New & Unread Topics

Topic Replies Views Activity
Docker artifacts being automatically deleted despite no policies/tasks enabled 0 45 Sep 2025
Sonatype Nexus Repository 3.85.0 Released 0 129 Oct 2025
Blob stores not getting cleaned (correctly) 2 149 Oct 2025
Proxy of Harbor docker registry stopped working 2 217 Nov 2025
how to configure docker registry path based routing in registries.conf 0 431 Sep 2025