Mysterious ENOTFOUND. How can I debug this?

[Teajey]

graphql-codegen is giving me this mysterious ENOTFOUND result even though this development endpoint works fine when I query it from Postman, or in the browser. Is there anything I can do to get more information about what's going here? Is it possible that it's a TLS or CORS issue?

[thomas@thomas-mbp ~/code/.../yarn_packages/solstice] master* DEBUG=1 VERBOSE=1 NODE_TLS_REJECT_UNAUTHORIZED=0 yarn run graphql-codegen                                              1 ↵
[00:21:13] Parse configuration [started]
[00:21:13] Parse configuration [completed]
[00:21:13] Generate outputs [started]
[00:21:13] Generate ./src/graphql/typed-document-nodes.ts [started]
[00:21:13] Load GraphQL schemas [started]
(node:8002) Warning: Setting the NODE_TLS_REJECT_UNAUTHORIZED environment variable to '0' makes TLS connections and HTTPS requests insecure by disabling certificate verification.
(Use `node --trace-warnings ...` to show where the warning was created)
TypeError: fetch failed
    at Object.processResponse (/Users/thomas/code/web/site/node_modules/undici/lib/fetch/index.js:183:23)
    at Fetch.fetchFinale (/Users/thomas/code/web/site/node_modules/undici/lib/fetch/index.js:937:17)
    at Fetch.mainFetch (/Users/thomas/code/web/site/node_modules/undici/lib/fetch/index.js:744:17)
    at processTicksAndRejections (node:internal/process/task_queues:96:5) {
  cause: Error: getaddrinfo ENOTFOUND api.localhost
      at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:71:26) {
    errno: -3008,
    code: 'ENOTFOUND',
    syscall: 'getaddrinfo',
    hostname: 'api.localhost'
  }
}
[00:21:13] Load GraphQL schemas [failed]
[00:21:13] → fetch failed
[00:21:13] Generate ./src/graphql/typed-document-nodes.ts [failed]
[00:21:13] → fetch failed
[00:21:13] Generate outputs [failed]
Something went wrong
[thomas@thomas-mbp ~/code/.../yarn_packages/solstice] master*

Here's what my .graphqlrc.yml looks likes:

schema: "https://api.localhost:8443/graphql"
documents: ./src/graphql/queries.graphql
extensions:
  codegen:
    generates:
      ./src/graphql/typed-document-nodes.ts:
        plugins:
          - typescript
          - typescript-operations
          - typed-document-node

[ardatan]

Make sure that endpoint is accessible within your terminal.

[Teajey]

This is a new concept to me, that the terminal is limited in what endpoints it can access. But it appears to be the case:

[thomas@thomas-mbp ~/code/.../yarn_packages/solstice] master* curl https://api.localhost:8443/graphql                                                                                                   127 ↵
curl: (6) Could not resolve host: api.localhost
[thomas@thomas-mbp ~/code/.../yarn_packages/solstice] master*

I'm not sure where to begin with changing this. It's inaccessible from my VS Code terminal and iTerm2

[Teajey]

Looks like it was my dodgy non-standard localhost subdomain that was the problem... The terminal wasn't allowed to access api.localhost. I'm going to have to find a better way to expose my API while in local development mode

[nthskyradiated]

ran into this problem. a support for subdomains would be nice

[Teajey]

In the end I set some port numbers in development to correspond to my subdomains in production, that seems to be a good way to go

[nthskyradiated]

cool. I think I'll do the same