TypeError: Cannot read property 'name' of undefined with simple typescript setup

[samuela]

Describe the bug
I'm trying to follow the intro tutorial but I'm hitting up on an error:

 Found 1 error

  ✖ src/generated/hasura-types.d.ts
    TypeError: Cannot read property 'name' of undefined
        at /Users/skainswo/dev/cuddlefish/vscode-extension/node_modules/graphql/type/introspection.js:622:17
        at Array.some (<anonymous>)
        at Object.isIntrospectionType (/Users/skainswo/dev/cuddlefish/vscode-extension/node_modules/graphql/type
/introspection.js:620:29)
...

You can check out the full log here: https://gist.github.com/samuela/93253c407de353d27ea8224a96757d73.

How does one set up a basic TS graphql-code-generator configuration?

To Reproduce
Steps to reproduce the behavior:

1. My GraphQL schema:

<long, complicated, and doesn't seem to be relevant. happy to provide on request tho!>

2. My GraphQL operations:

# src/queries.graphql
mutation StartThread(
  $repoIds: [String!]!
  $commitHash: String!
  $filePath: String!
  $lineNumber: Int!
  $body: String!
) {
  StartThread(
    repoIds: $repoIds
    commitHash: $commitHash
    filePath: $filePath
    lineNumber: $lineNumber
    body: $body
  )
}

3. My codegen.yml config file:

overwrite: true
schema: "http://localhost:8080/v1/graphql"
documents: "src/**/*.graphql"
generates:
  src/generated/hasura-types.d.ts:
    plugins:
      - "typescript"

Expected behavior
The setup tutorial to "just work."

Environment:

• OS: macOS 11.6
• @graphql-codegen/...:

		"@graphql-codegen/cli": "2.2.1",
		"@graphql-codegen/introspection": "2.1.0",
		"@graphql-codegen/typescript": "^2.2.4",
		"@graphql-codegen/typescript-document-nodes": "2.1.6",
		"@graphql-codegen/typescript-graphql-files-modules": "2.1.0",
		"@graphql-codegen/typescript-operations": "2.1.8",

• NodeJS: v15.14.0

Additional context

[samuela]

Possibly relevant: "graphql": "^15.6.1"

[samuela]

Actually, I believe that this was due to a weird GraphQL schema. I recently changed the schema slightly in a way that should've made no difference and the error has disappeared. I'll close for now, and open a new issue if I'm able to find a concrete reproduction.