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.
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.