Multiple npm registries support

[KingOfTac]

Does esm.sh support targeting multiple npm registries when self hosting, or does configuring a private registry mean it pulls from the private registry in addition to the default npm registry?

[ije]

it supports multiple registries as scopes in next version, and it won't pull packages from registry.npmg.org if you specify a private global registry:

{
  // The global npm registry, default is "https://registry.npmjs.org/".
  "npmRegistry": "https://registry.npmjs.org/",

  // The npm access token for the global npm registry, default is empty.
  "npmToken": "",

  // These two fields are used for basic authentication towards the global npm registry,
  // default for both is empty.
  "npmUser": "",
  "npmPassword": "",

  // Registries for scoped packages. This will ensure packages with these scopes get 
  // downloaded from specific registry, default is empty.
  "npmRegistries": {
    "@scope_name": {
      "registry": "https://your-registry.com/",
      "token": "xxx",
      "user": "username",
      "password": "xxx"
    }
  }
}