Skip to content
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

[[email protected]] reintroduces error: ReactDOMServer does not yet support Suspense #2239

Closed
Swiftwork opened this issue Feb 2, 2022 · 3 comments · Fixed by #2237
Closed
Labels
bug 🐛 Oh no! A bug or unintented behaviour.

Comments

@Swiftwork
Copy link

Package [email protected] reintroduces the previous suspense error when paired with next and next-urql:

Error: ReactDOMServer does not yet support Suspense

urql version & exchanges:

"dependencies": {
  "graphql": "16.3.0",
  "next": "12.0.10",
  "next-urql": "3.3.2",
  "react": "17.0.2",
  "react-dom": "17.0.2",
  "react-is": "17.0.2",
  "urql": "2.1.0"
},

Steps to reproduce

  1. Setup a new next project from scratch with yarn create next-app
  2. Add urql and dependencies yarn add next-urql react-is urql graphql
  3. Create a page using withUrqlClient(...) and ssr: true
  4. useQuery(...) to fetch data from a GraphQL endpoint
  5. Run the project with yarn dev and observe the error

Expected behavior

Continue working the same as version 2.0.6 and not cause the error above.

Actual behavior

Repository with reproduction of error

@Swiftwork Swiftwork added the bug 🐛 Oh no! A bug or unintented behaviour. label Feb 2, 2022
@JoviDeCroock
Copy link
Collaborator

This should be fixed in 2.1.3, feel free to reopen if the issue persists, the linked PR's contain the reproduction used

@Swiftwork
Copy link
Author

Great work @JoviDeCroock I'll check it out tomorrow!

@Swiftwork
Copy link
Author

I can confirm that the changes have resolved this issue :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug 🐛 Oh no! A bug or unintented behaviour.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants