you now have to write import statements for all schema related files in graphql/schema.ts.
If you do that then both GraphQL endpoints (localhost:4000/graphql + localhost:3000/api/graphql) work. However, when you omit the manual import statements in graphql/schema.ts it still continues to work at localhost:4000/graphql, however it no longer works for localhost:3000/api/graphql. For me not dealing with imports in graphql/schema.ts seemed like a nice behaviour of the nexus framework. I was trying to understand if I could avoid the import statements somehow in nextjs localhost:3000/api/graphql?
I'm not sure why it would continue to work with Nexus dev server's /graphql route, but my guess is that it's due to some caching not being invalidated by Nexus (probably a bug, I'll try to dig into it). The correct behavior should be it fails as well. :)
Edit: Normally, Nexus actually scans the entire project for import {schema} from 'nexus', if an entry point is not specified.
Yes, that's exactly what I am talking about,
you now have to write import statements for all schema related files in
graphql/schema.ts.If you do that then both GraphQL endpoints (localhost:4000/graphql + localhost:3000/api/graphql) work. However, when you omit the manual import statements in
graphql/schema.tsit still continues to work atlocalhost:4000/graphql, however it no longer works forlocalhost:3000/api/graphql. For me not dealing with imports ingraphql/schema.tsseemed like a nice behaviour of the nexus framework. I was trying to understand if I could avoid the import statements somehow in nextjs localhost:3000/api/graphql?I'm not sure why it would continue to work with Nexus dev server's
/graphqlroute, but my guess is that it's due to some caching not being invalidated by Nexus (probably a bug, I'll try to dig into it).The correct behavior should be it fails as well. :)Edit: Normally, Nexus actually scans the entire project for
import {schema} from 'nexus', if an entry point is not specified.I think the problem you are encountering is because somehow Nexus imported the external schema after the Nexus
apphas assembled. Actually, when working with Next.js, it's not recommended to have multiple files that import the same part (like use, schema) from Nexus.