I want to use a Nexus repo as a proxy for my npmjs.org requests when I do “npm i”, where I explicitly can specify what packages I want to allow.
So I’m trying to set up routing rules for that purpose.

E.g. for the package zone.js I see in outbound-request.log, that there are two requests.
The first one is: https://registry.npmjs.org/zone.js
And the second: https://registry.npmjs.org/zone.js/-/zone.js-0.13.3.tgz

The following matcher in the routing rules is too restrictive, so that zone.js is not installed:
./zone.js-0.13.

But if I change the matcher to:
./zone.js.
both requests pass through.

I’m afraid, it’s just the way how packages are fetched from npmjs.org, meaning the first request is just the package name, and the second request contains the version info.

Or is there a possibility to make the rules more restrictive?

I use Sonatype Nexus Repository OSS 3.63.0-01

Any ideas or thoughts would be appreciated.