Details
Description
As a note of inconsistency when you request <npmrepoid>/-/all from Nexus, it returns a package list for every package available, which includes a root package "-"
{ "name": "-", "description": "NX registry root package", "versions": { "0.0.0": "latest" }, "dist-tags": { "latest": "0.0.0" } }
The official registries don't identify such a package.
In cases where a tool wishes to request metadata for packages from Nexus, making the following request, always returns 404 not found:
> curl -4 http://localhost:8081/nexus/content/groups/npm/- <html> <head> <title>404 - Path /- not found in group repository "npm" [id=npm].</title> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"/> <link rel="icon" type="image/png" href="http://localhost:8081/nexus/favicon.png"> <!--[if IE]> <link rel="SHORTCUT ICON" href="http://localhost:8081/nexus/favicon.ico"/> <![endif]--> <link rel="stylesheet" href="http://localhost:8081/nexus/static/css/Sonatype-content.css?2.11.2-SNAPSHOT" type="text/css" media="screen" title="no title" charset="utf-8"> </head> <body> <h1>404 - Path /- not found in group repository "npm" [id=npm].</h1> <p>Path /- not found in group repository "npm" [id=npm].</p> </body> </html>
Expected: Nexus should not include the "-" package entry in the response to GET /-/all metadata.