Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Node.js, PHP and APIs

NestJS GraphQL cannot work out the output type of a field or query

ErrorCannot determine a GraphQL output type for the "<name>". Make sure your class is decorated with an appropriate decorator.

Short answer

In code-first mode Nest reads TypeScript types through decorators, and arrays, promises and unions disappear at runtime. When the mapping is ambiguous, you must give the decorator a type function: @Field(() => [Post]) for lists, @Query(() => Author) for resolvers.

  • Applies to NestJS 11, @nestjs/graphql 13, Apollo driver, Node.js 22
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 1Find out which cause you have

    The message names the field or resolver method. Open that class member and look at the decorator above it: does it have a type function?

    grep -rn "@Field\|@Query\|@ResolveField\|@Mutation" src
  2. 2Match what you see, then jump to its fix

    1. 1The failing member is a property typed Something[]A list field has no array type functionFix
    2. 2The failing member is a @Query, @Mutation or @ResolveField with no function, or one that returns a Promise, an array or a unionA resolver method returns a type that cannot be inferredFix

What does the error look like?

  • Cannot determine a GraphQL output type for the "<name>". Make sure your class is decorated with an appropriate decorator.

Cause 1 of 2

A list field has no array type function

1Check

TypeScript reflects an array property as plain Array, so Nest cannot see the item type. The docs say that when the field is an array, you must indicate the array type in the type function.

grep -rn -B1 "\[\];" src --include=*.ts

2Fix

Give @Field a type function that returns the item type in square brackets.

@ObjectType()
export class Author {
  @Field(() => [Post])
  posts: Post[];
}

3Verify

The app starts and the schema file lists posts as a list.

npm run start:dev

Confirmed by docs.nestjs.com

Did this fix it?

Cause 2 of 2

A resolver method returns a type that cannot be inferred

1Check

The type function is required when the mapping between TypeScript and GraphQL is ambiguous. A resolver can return its value directly or as a promise, so state the GraphQL type on the decorator.

grep -rn "@Query()\|@Mutation()\|@ResolveField()" src

2Fix

Pass the return type to the decorator. Wrap it in brackets for lists.

@Query(() => Author)
async author(@Args('id', { type: () => Int }) id: number) {
  return this.authorsService.findOneById(id);
}

@Query(() => [Author])
authors() {
  return this.authorsService.findAll();
}

3Verify

Open the GraphQL endpoint and run the query: the type resolves.

curl -s http://localhost:3000/graphql -H "Content-Type: application/json" -d '{"query":"{ authors { id } }"}'

Confirmed by docs.nestjs.com

Did this fix it?

How do I stop it coming back?

  • Write the type function on every @Field, @Query and @Mutation by habit, even when it looks optional.
  • Mark optional fields with { nullable: true }; fields are non-nullable by default.
  • Commit the generated schema file (autoSchemaFile) so a changed type shows up in code review.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.

Which stack is behind this page?

Projects of mine built on the same technologies:

Related fixes

Back end

IntelliJ IDEA breakpoints are ignored in a NestJS app

No 'Debugger listening' line appears when the NestJS app starts

IntelliJ can only debug a NestJS app when the Node.js process runs with the inspector on and the IDE attaches to its port.

4 causes, each with a fix

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.