panates / rman / 39683077053

95%

main: 95%

push

github

feat(deps): move npm aliases under the package they name; hold only the move npm's verdict names

An `npm:<name>@^x` alias was skipped outright and silently - it is no semver
range, so it was neither moved nor listed - and a plain peer of the same
name beside it was asked of npmjs.org under its own name. Measured on
abisena/syncbridge-iomt: host modules declared as a peer
`"@syncbridge/hl7": "^2.0.0"` plus a dev
`"npm:@sbext/syncbridge__hl7@^2.0.0"` from a mirror; npmjs.org stops at
1.2.1, so a 2.1.0 on the mirror would have read "up to date". Now the versions
are asked of the aliased package (through the repository's .npmrc, so the
mirror answers), every field of the name is held to them, and the rewrite
keeps the `npm:<name>@` prefix - the alias and the peer move together.

Blame read only `name@version` and missed npm's other spelling of a move,
the declared range (`dev x@"^2.2.0" from the root project`): the verdict
matched nothing and every move the output mentioned was held under that one
line, @syncbridge/testing with syncbuild's reason (also syncbridge-iomt). Both
forms are matched now, and the reason carries npm's "Conflicting peer
dependency" line.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

4755 of 5199 branches covered (91.46%)

Branch coverage included in aggregate %.

83 of 83 new or added lines in 1 file covered. (100.0%)

25066 of 26221 relevant lines covered (95.6%)

264.67 hits per line