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.

Build fails: "TypeError: autoGeneratedSchema.toConfig is not a function"

See original GitHub issue

I’m submitting a…


[ ] Regression 
[x] Bug report
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead post your question on Stack Overflow.

Current behavior

After running an npm audit and updating nestjs/graphql, I am met with this error: (node:36595) UnhandledPromiseRejectionWarning: TypeError: autoGeneratedSchema.toConfig is not a function at GraphQLFactory.<anonymous>

nestjs/common and core were both updated as well, and the issue persists. I updated version numbers manually after seeing this error to isolate the issue, and it seems to be coming from something within nestjs/graphql.

Expected behavior

App builds successfully

Minimal reproduction of the problem with instructions

updated from

    "@nestjs/common": "6.0.1",
    "@nestjs/core": "6.0.1",
    "@nestjs/graphql": "6.0.1",

    "@nestjs/common": "6.5.3",
    "@nestjs/core": "6.5.3",
    "@nestjs/graphql": "6.4.2",

What is the motivation / use case for changing the behavior?

For whatever reason, autoGeneratedSchema.toConfig() is throwing a TypeError claiming that toConfig() is not a function. Because of this, the build fails.

Environment


Nest version: 5.7.1
 
For Tooling issues:
- Node version: 10.15.0
- Platform:  Mac

Others:
MacOS Mojave v 10.14.5
Visual Studio Code

Issue Analytics

State:
Created 4 years ago
Comments:6 (3 by maintainers)

Top GitHub Comments

1reaction

KristenLeachcommented, Jul 23, 2019

Working on this between my regular job hours. 😬 With a minimal repo with very little data to add to the schema, the error does not happen. Somewhere in my massive work repo during the schema build the error is getting thrown with the updated packages. I will keep digging to see if I can isolate where it is coming from. I traced it back to where .toConfig is being called from graphql, but what is causing the error is still tbd.

0reactions

lock[bot]commented, Apr 25, 2020

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

Top Results From Across the Web

nodejs get error 'originalType.toConfig is not a function'

I am trying to make a test run of an application using graphql. But I get the error. types resolvers src/api/Hello/sayBye/sayBye.graphql

Federation2 update issue - Help - Apollo GraphQL

while upgradation I am facing issue in core-schema which is internally used by federation internal. "return this.node<DefinitionNode>(this.

Renovate Bot Package Diff

+ export declare function Extensions(value: Record<string, unknown>): MethodDecorator ... throw new Error('GraphQL schema has not yet been created. ' +.

Graphql is not a function error : r/gatsbyjs - Reddit

I am getting this error and I am trying to learn how to automate the page ... File: gatsby-node.js:3:25 TypeError: graphql is not...

Full text of "Barmaja0000025" - Internet Archive

Increasingly, you might build your next Rails application using a non-relational ... and the use of SQL functions not already built into Active...