Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[Bug]: nestjs/graphql 9 breaks the interceptro

See original GitHub issue

Bug Report

Current behavior

[2021-08-26T14:03:10.537Z] [ERROR] [eris] [development] [40475]  [ExceptionsHandler] TypeError: Cannot set property 'requestId' of undefined
    at GraphQLParser.setRequestId (/Users/roderik/Development/bpaas/node_modules/@ogma/platform-express/lib/express-interceptor.service.js:32:23)
    at DelegatorService.setRequestId (/Users/roderik/Development/bpaas/node_modules/@ogma/nestjs-module/lib/interceptor/providers/delegator.service.js:27:22)
    at OgmaInterceptor.intercept (/Users/roderik/Development/bpaas/node_modules/@ogma/nestjs-module/lib/interceptor/ogma.interceptor.js:40:23)
    at /Users/roderik/Development/bpaas/node_modules/@nestjs/core/interceptors/interceptors-consumer.js:23:36
    at InterceptorsConsumer.intercept (/Users/roderik/Development/bpaas/node_modules/@nestjs/core/interceptors/interceptors-consumer.js:25:24)
    at target (/Users/roderik/Development/bpaas/node_modules/@nestjs/core/helpers/external-context-creator.js:77:60)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at /Users/roderik/Development/bpaas/node_modules/@nestjs/core/helpers/external-proxy.js:9:24
    at Object.createAsyncIterator (/Users/roderik/Development/bpaas/node_modules/@nestjs/graphql/dist/utils/async-iterator.util.js:6:27)

Issue Analytics

State:
Created 2 years ago
Comments:5 (5 by maintainers)

Top GitHub Comments

1reaction

roderikcommented, Sep 7, 2021

Yeah sorry, we are in the last 10% stretch of release (90% of the work still to do) so I quickly ripped out ogma and went back to the included logger until we get our heads above water.

0reactions

jmcdo29commented, Apr 28, 2022

I have @nestjs/grpahql@9.1.1 being used in the integration tests and have no issue with it. @nestjs/graphql@10 might be a different story with the built in apollo and mercurius support, but that should be a different issue. I’m going to close this as it looks resolved to me, if not and you can provide a minimum reproduction, please do so

Top Results From Across the Web

@nestjs/graphql 7.9.8 breaks retrieving the request ... - GitHub

I have a few Guards and Interceptors that access the Express request. I added it to the GraphQL context like so: GraphQLModule.forRootAsync({ ...

NestJS problem with ClassSerializerInterceptor in GraphQL

Without interceptor, everything is working fine (except that password is still visible). Any ideas what I'm doing wrong? graphql · nestjs ...

Other features | NestJS - A progressive Node.js framework

Nest is a framework for building efficient, scalable Node.js server-side applications. It uses progressive JavaScript, is built with TypeScript and combines ...

Handling GraphQL errors like a champ with unions and ...

Error handling can be frustrating in GraphQL. This post shows you how to use unions and interfaces to handle errors in a more...

How To Use NestJS Logger [Plus Pino Setup] - Tom Ray

Learn how to use the NestJS logger to add automatic HTTP request logging (and other cool capabilities) to your application.