So it turns out adding config to allow for a per-scoped-package registry to be configured was a one-liner. Still skunkworks. We'll see if this ever makes it past testing. Un-scoped may never happen, we'll see. Don't make me regret tooting this.

Screenshot showing output from production npm and a local copy showing a different registry being attempted for a single scoped package based on a new config
0

If you have a fediverse account, you can quote this note from your own instance. Search https://mastodon.social/users/Gar/statuses/115273728981274252 on your instance and quote it. (Note that quoting is not supported in Mastodon.)