Changing group member order changes what users can see in the Browse page for NPM group repository.
- Create npm-proxy, npm-hosted, npm-group
- Download something via npm-proxy, for example, lodash-4.17.19.tgz
- Upload the downloaded asset into npm-hosted.
- Check the npm-group repo, and it shows "lodash" directory and lodash-4.17.19.tgz file
- From Browse, go to the npm-proxy repo and delete lodash-4.17.19.tgz asset (not "lodash" directory)
- From the npm-group repository setting, make "npm-proxy" first.
- Browse npm-hosted and check lodash-4.17.19.tgz is visible.
- Browse npm-group, and you can't see any lodash-4.17.19.tgz which should exist under npm-hosted.
As of this typing, there is no easy workaround to delete this orphaned metadata asset from npm-proxy repository.
The npm group repository should show correct contents under Browse regardless of the group member order.