Simon Proper

Using useMemo worked for me as well, however the brackets and parentheses in https://github.com/zenoamaro/react-quill/issues/688#issuecomment-793441268 is not correct. This is what worked for me: ```js const modules = useMemo(() => ({...

Sadly the same is true for using both the latest react and react-dom packages, as can be seen in this [stackblitz](https://stackblitz.com/edit/vercel-next-js-snerz6?file=app/page.tsx). (Updated the issue with the react 18.3 stackblitz) In...

Sadly it doesn't affect this case, if you look in the app/page.tsx file, the fetch is already inside a separate async function outside the component. This is also copied directly...

@himyjan Thank you for that, good workaround for now! It also seems as they removed the example from the docs as well.

Do we have any updates on this issue? Ran into the same problem as above today when using the hook inside a dynamic route using the pages directory. Sadly to...

@franky47 I did indeed have the wrong version of next, however the problem seems to persists even after updating to next v.14.0.1 and next-usequerystate 1.10.0. I will see if I...

@franky47 So I managed to reproduce the issue. It is occurring when you are setting a value with the option `shallow:false` inside of a dynamic page. Have a look at...

@franky47 I can confirm that it works with your latest changes in `1.10.2-beta-1`. Nice work! Forked the reproduction and updated the version if you want to test out for yourself:...