Resolution: Not A Bug
Affects Version/s: 3.15.2, 3.16.0
Fix Version/s: None
Environment:Sonatype Nexus Repository Manager OSS 3.16.0-01
Linux server running Nexus. MacOS client running yarn/npm commands.
I have set up a NPM proxy repository that proxies https://registry.npmjs.org
It seems that scoped packages e.g @sentry/browser are not working. All the non scoped packages are working.
My package.json has dependency
I have set up .yarnrc to connect my repository. When running for example
yarn is trying to fetch this request https://my-repo/repository/npm-group/@sentry%2fbrowser where Nexus responds with 404. npm will make identical query and gets 404 also from the Nexus. Here the / in package name is URL encoded
It seems that Nexus expects the URL to be https://my-repo/repository/npm-group/@sentry/browser. At least this will not return 404. Here the / in the package name is NOT URL encoded.
Yarn outdated is just an example. It seems that there is same behavior whenever yarn actually tries to fetch the package data from the Nexus repository.
This happens at least with Nexus OSS 3.16.0-01and 3.15.2-01