···11+---
22+'next-urql': minor
33+---
44+55+Add option called `neverSuspend` to disable `React.Suspense` on next.js.
+5
docs/advanced/server-side-rendering.md
···241241Unless the component that is being wrapped already has a `getInitialProps` method, `next-urql` won't add its own SSR logic, which automatically fetches queries during
242242server-side rendering. This can be explicitly enabled by passing the `{ ssr: true }` option as a second argument to `withUrqlClient`.
243243244244+When you are using `getStaticProps`, `getServerSideProps`, or `getStaticPaths`, you should opt-out of `Suspense` by setting the `neverSuspend` option to `true` in your `withUrqlClient` configuration.
245245+your `withUrqlClient`.
246246+During the prepass of your component tree `next-urql` can't know how these functions will alter the props passed to your page component. This injection
247247+could change the `variables` used in your `useQuery`. This will lead to error being thrown during the subsequent `toString` pass, which isn't supported in React 16.
248248+244249### Resetting the client instance
245250246251In rare scenario's you possibly will have to reset the client instance (reset all cache, ...), this is an uncommon scenario
+5
packages/next-urql/README.md
···246246component has children using `getInitialProps` but that component itself is not and you want to opt in to this behavior you'll have to set the second argument of
247247`withUrqlClient`, this means `withUrqlClient(() => clientOptiosn, { ssr:true })`.
248248This measure is available so we can support `getStaticProps`, ...
249249+250250+When you are using `getStaticProps`, `getServerSideProps`, or `getStaticPaths`, you should opt-out of `Suspense` by setting the `neverSuspend` option to `true` in your `withUrqlClient` configuration.
251251+your `withUrqlClient`.
252252+During the prepass of your component tree `next-urql` can't know how these functions will alter the props passed to your page component. This injection
253253+could change the `variables` used in your `useQuery`. This will lead to error being thrown during the subsequent `toString` pass, which isn't supported in React 16.