-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GraphQL doesn't work properly with turbopack #6498
Labels
Comments
happens here as well. same versions.
|
This is also present for me, it appears that every request using variables fails. Using dependencies: {
"payload": "3.0.0-beta.60",
"next": "15.0.0-canary.64",
"graphql": "^16.9.0"
} Setting resolutions/overrides does not solve the issue. Switching back to webpack does fix it of course. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Link to reproduction
No response
Payload Version
beta.36
Node Version
v20.11.1
Next.js Version
15.0.0-rc.0
Describe the Bug
When running NextJS like it's configured in this demo repo, and run it with turbopack by adding
turbo
to thedev
script inpackage.json
, I get a conflict error when making a request to GraphQL.Note that without the
--turbo
flag it works. I initially came across this error by using Next 14 with React 18, because I wanted to integrate this in my current project, so the issue also applies to these versions. It applies to both mongodb and postgres adapters.Reproduction Steps
.env.example
to.env
start-database.sh
dev
command inpackage.json
to"cross-env NODE_OPTIONS=--no-deprecation next dev --turbo"
http://localhost:3000/api/graphql-playground
where I would expect to receive a Forbidden 403 gql error. I've also tried this with custom collections where a set the access:read to open, same result
(page: 1)
, It worksAdapters and Plugins
db-mongodb, db-postgres
The text was updated successfully, but these errors were encountered: