request to url failed, reason: connect ECONNR EFUSED 127.0.0.1:8001

Describe the bug

To Reproduce Steps to reproduce the behavior:

1. Start a blank Svelte project
2. Install required dependencies:

npm install @graphql-codegen/cli -D

npm i @graphql-codegen/typescript @graphql-code
gen/typescript-operations -D

npm i @graphql-codegen/typescript-urql @graphql
-codegen/urql-introspection @graphql-codegen/urql-svelte-operations-stor
e -D

npm i @urql/svelte urql graphql

1. Create a codegen.yml config:

overwrite: true
schema: "http://localhost:8001/"
documents: "src/**/*.graphql"
config:
  withHooks: false
generates:
  src/graphql/generated/graphql.ts:
    plugins:
      - "typescript"
      - "typescript-operations"
      - "typescript-urql"
      - "urql-svelte-operations-store"

1. Create a script in package.json for codegen:

{
...
"scripts": {
  ...
  "generate": "graphql-codegen --config codegen.yml"
  ...
}
...
}

1. Have a backend API running on localhost:8001

2. Run npm run generate

3. Get the error:

> generate
> graphql-codegen --config codegen.yml

  ✔ Parse configuration
  ❯ Generate outputs
    ❯ Generate src/graphql/generated/graphql.ts
      ✖ Load GraphQL schemas
        → Failed to load schema
        Load GraphQL documents
        Generate


 Found 1 error

  ✖ src/graphql/generated/graphql.ts
    Failed to load schema from http://localhost:8001/:

        request to http://localhost:8001/ failed, reason: connect ECONNR
EFUSED 127.0.0.1:8001
        FetchError: request to http://localhost:8001/ failed, reason: co
nnect ECONNREFUSED 127.0.0.1:8001
    at ClientRequest.<anonymous> (/workspace/node_modules/node-fetch/lib
/index.js:1491:11)
    at ClientRequest.emit (node:events:390:28)
    at Socket.socketErrorListener (node:_http_client:447:9)
    at Socket.emit (node:events:390:28)
    at emitErrorNT (node:internal/streams/destroy:157:8)
    at emitErrorCloseNT (node:internal/streams/destroy:122:3)
    at processTicksAndRejections (node:internal/process/task_queues:83:2
1)

        GraphQL Code Generator supports:
          - ES Modules and CommonJS exports (export as default or named 
export "schema")
          - Introspection JSON File
          - URL of GraphQL endpoint
          - Multiple files with type definitions (glob expression)
          - String in config file

        Try to use one of above options and run codegen again.
    Error: Failed to load schema
        at loadSchema (/workspace/node_modules/@graphql-codegen/cli/bin.
js:495:15)
        at processTicksAndRejections (node:internal/process/task_queues:
96:5)
        at async /workspace/node_modules/@graphql-codegen/cli/bin.js:907
:55
        at async Task.task (/workspace/node_modules/@graphql-codegen/cli
/bin.js:761:17)
    Error: Failed to load schema
        at loadSchema (/workspace/node_modules/@graphql-codegen/cli/bin.
js:495:15)
        at processTicksAndRejections (node:internal/process/task_queues:
96:5)
        at async /workspace/node_modules/@graphql-codegen/cli/bin.js:907
:55
        at async Task.task (/workspace/node_modules/@graphql-codegen/cli
/bin.js:761:17)


Something went wrong

Environment:

• OS: Containerized debian installed in Artix Linux.
• Codegen versions “@graphql-codegen/cli”: “^1.9.0”, “@graphql-codegen/typescript”: “^2.4.3”, “@graphql-codegen/typescript-operations”: “^2.2.4”, “@graphql-codegen/typescript-urql”: “^3.5.1”, “@graphql-codegen/urql-introspection”: “^2.1.1”, “@graphql-codegen/urql-svelte-operations-store”: “^1.1.10”,
• Node version: v16.13.2

UPDATE: apparently this happens due to my containerized app. If I run the command in my local repo instead of inside my container it works just fine. Might need a workaround for this

[Lucasmiguelmac]

Yes, it seems to be a container-related thing. I’ll continue close the issue and try set up the networking. I might reopen it if the doubtious case that it is something else happens. Thank you very much

[ardatan]

I’ll take a look at the reproduction but in the meanwhile could you make sure that URL is accessible with cURL inside the container?