@aoxborrow/registrar-client 0.2.0 → 0.4.0

package/README.md

@@ -4,6 +4,7 @@
 [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
 [![Node.js](https://img.shields.io/badge/node-%3E%3D20.0.0-brightgreen.svg)](https://nodejs.org)
 [![TypeScript](https://img.shields.io/badge/TypeScript-5.9-blue.svg)](https://www.typescriptlang.org)
+[![Sponsor](https://img.shields.io/badge/Sponsor-%E2%9D%A4-ea4aaa?logo=githubsponsors&logoColor=white)](https://github.com/sponsors/aoxborrow)
 
 > One consistent, fully-typed TypeScript interface to many domain registrar APIs.
 

package/dist/index.cjs

@@ -258,7 +258,7 @@ var RegistrarClient = class {
         try {
           const detail = await this.provider.getDomain(name, opts);
           let merged = { ...domains[index], ...detail };
-          if (merged.nameservers.length === 0) {
+          if (merged.nameservers.length === 0 && this.provider.requiresNameserversFetch) {
             try {
               const nameservers = normalizeNameservers(
                 await this.provider.getNameservers(name, opts)
@@ -646,6 +646,11 @@ var BaseRegistrar = class {
   supports(feature) {
     return this.features.includes(feature);
   }
+  // See Registrar.requiresNameserversFetch. Defaults true, so a provider
+  // whose getNameservers hits a real endpoint keeps the enrichment fallback
+  // without opting in; the providers whose getNameservers just re-reads getDomain
+  // override this to false to drop the redundant call.
+  requiresNameserversFetch = true;
   constructor(credentials, httpConfig, options) {
     const { environment = "production", ...clientOptions } = options ?? {};
     this.credentials = credentials;
@@ -1716,6 +1721,9 @@ ${bodyStr}`;
     if (!data.domain_info) throw new NotFoundError(`Dynadot: domain '${domainName}' not found`);
     return data.domain_info;
   }
+  // getNameservers re-reads getDomain (domain_info carries NS inline; no separate
+  // endpoint), so listing enrichment gains nothing from the fallback — skip it.
+  requiresNameserversFetch = false;
   async getNameservers(domainName, opts) {
     const domain = await this.getDomain(domainName, opts);
     return domain.nameservers;
@@ -3036,12 +3044,24 @@ var GoDaddyRegistrar = class _GoDaddyRegistrar extends BaseRegistrar {
   name = "godaddy";
   static displayName = "GoDaddy";
   static website = "godaddy.com";
-  static helpText = 'Authenticate one of two ways. For production, create a Personal Access Token (PAT) at https://developer.godaddy.com and pass it as `apiToken` \u2014 this enables the modern v3 API. For sandbox testing, create OTE (test environment) keys and pass `apiKey` + `apiSecret` with { environment: "sandbox" }; OTE only exposes the legacy v1 API. The sso-key (API Key/Secret) scheme is deprecated by GoDaddy in 2026. Domain forwarding uses the v2 customer-scoped API \u2014 set `customerId` to your GoDaddy customer UUID, or to your numeric shopper/account ID (which the client resolves to the UUID via an sso-key-authenticated lookup).';
+  static helpText = "Create a Personal Access Token (PAT) at https://developer.godaddy.com and paste it here. The PAT is GoDaddy's modern credential: it unlocks the v3 API (discovery, registration, DNS, nameservers) and also authenticates the legacy v1 API for management operations (renew, transfer, auto-renew, lock, privacy, contacts) \u2014 one token covers everything.";
+  // Only the PAT is exposed for configuration — it is the sole credential
+  // GoDaddy recommends going forward, and it covers every production operation.
+  //
+  // The legacy `apiKey` + `apiSecret` (sso-key) pair and the `customerId` field
+  // are intentionally NOT advertised here. The code that consumes them is kept
+  // (see `authHeader`, `useV3`, `resolveCustomerId`, and the forwarding methods)
+  // so OTE/sandbox testing and direct programmatic use still work when those
+  // values are passed in credentials explicitly. But because they are no longer
+  // configurable, two capabilities are effectively unreachable through normal
+  // (config-driven) setup:
+  //   - OTE/sandbox, which needs an sso-key (`apiKey` + `apiSecret`), and
+  //   - domain forwarding, which needs `customerId` (a customer UUID), plus an
+  //     sso-key to resolve a numeric shopper ID to that UUID.
+  // GoDaddy is deprecating the sso-key scheme in 2026, so this is the direction
+  // of travel regardless.
   static configFields = [
-    { name: "apiToken", label: "API Token (PAT)", type: "password", required: false },
-    { name: "apiKey", label: "API Key", type: "password", required: false },
-    { name: "apiSecret", label: "API Secret", type: "password", required: false },
-    { name: "customerId", label: "Customer ID or Shopper ID", type: "text", required: false }
+    { name: "apiToken", label: "API Token (PAT)", type: "password", required: true }
   ];
   // GoDaddy's OTE ("Operational Test Environment") is its sandbox
   static supportsSandbox = true;
@@ -3159,6 +3179,9 @@ var GoDaddyRegistrar = class _GoDaddyRegistrar extends BaseRegistrar {
     });
     return this.toDomain(d);
   }
+  // getNameservers re-reads getDomain (GoDaddy has no dedicated NS endpoint), so
+  // listing enrichment gains nothing from the fallback — skip it.
+  requiresNameserversFetch = false;
   async getNameservers(domainName, opts) {
     const domain = await this.getDomain(domainName, opts);
     return domain.nameservers;
@@ -5060,6 +5083,9 @@ var NameSiloRegistrar = class extends BaseRegistrar {
       nameservers: extractNsHosts(r.nameservers)
     });
   }
+  // getNameservers re-reads getDomain (getDomainInfo carries NS; no separate
+  // endpoint), so listing enrichment gains nothing from the fallback — skip it.
+  requiresNameserversFetch = false;
   async getNameservers(domainName, opts) {
     const domain = await this.getDomain(domainName, opts);
     return domain.nameservers;
@@ -6301,6 +6327,9 @@ var SpaceshipRegistrar = class extends BaseRegistrar {
   async getDomain(domainName, opts) {
     return this.toDomain(await this.getRaw(domainName, opts));
   }
+  // getNameservers reads the same getRaw payload as getDomain (no dedicated NS
+  // endpoint), so listing enrichment gains nothing from the fallback — skip it.
+  requiresNameserversFetch = false;
   async getNameservers(domainName, opts) {
     const d = await this.getRaw(domainName, opts);
     return d.nameservers?.hosts ?? [];