3 ms·
Scopes were only introduced in NPM 2, and iirc it's still an optional feature. Companies that used NPM early on may have opted to never use those. But that's j
by Cthulhu_ 6y ago
Scopes were only introduced in NPM 2, and iirc it's still an optional feature. Companies that used NPM early on may have opted to never use those.
But that's just NPM, it's an issue in all of the mentioned package managers.
- high_byte 6y agotrue. simplest solution is just always prioritize internal over external.
- joepie91_ 6y agoThis is exactly what Verdaccio does, and has been doing since forever. It frankly kind of boggles my mind that other private registry implementations don't.
- thw0rted 6y agoJust "prioritizing" doesn't fix it, you have to limit scoped packages to be provided by a single (trusted, internal) repo. Otherwise, what do you do when internal offers v1.2.3 but external says it has v1.99.99?