NexusGraphQLSchema is no longer a GraphQLSchema with nexus@1.2.0-next.17
See original GitHub issueThe NexusGraphQLSchema
object no longer satisfies GraphQLSchema
with nexus@1.2.0-next.17
.
const schema: GraphQLSchema = makeSchema({ ... })
gives the error
Type ‘NexusGraphQLSchema’ is missing the following properties from type ‘GraphQLSchema’: _queryType, _mutationType, _subscriptionType, _directives, and 3 more.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:5
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Schema - GraphQL Nexus
We will now begin exploring the GraphQL schema building parts of the schema component. Having prior knowledge of GraphQL language itself will greatly...
Read more >Building a GraphQL schema using Nexus, Prisma and Nextjs
In this video, you'll learn how to add support for Pagination on the Server using Nexus and how to send a paginated query...
Read more >GraphQL schema basics - Apollo GraphQL Docs
Your GraphQL server uses a schema to describe the shape of your available data. This schema defines a hierarchy of types with fields...
Read more >Nexus + Prisma: the Future of Backend - zach.codes
Installing the dependencies · Setup Prisma · Nexus GraphQL Schema · Start the server · Adding a CRUD resolver · Spinning up Postgres...
Read more >GraphQL Code Libraries, Tools and Services
Real-Time with GraphQL for any GraphQL schema or transport. ... This way you can make sure your application will remain quick, and no...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
This is now fixed as of v1.3.0. Thanks for your great work as always, @tgriesser!
Downgrade graphql from v16 to v15.8 resolved this.