Skip to content

GraphQL Instance Conflict in Next.js App Router with GraphQL Yoga #3870

Closed Answered by blagoySimandov
blagoySimandov asked this question in Q&A
Discussion options

You must be logged in to vote

Moved the graphql backend to a separate service outside of next.js and this solved the issue.
Seems that the shared backend/frontend codebase of next was causing the issue.

EDIT: Still not sure why/how to solve the issue in Next without the need of another service.

Replies: 2 comments

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Answer selected by blagoySimandov
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants