Has anyone been able to properly figure out the hydration issues for feature flags using Next.js and the pages router? Documentation doesn't seem to address this properly,

useFeatureIsOn

and

IfFeatureEnabled

both throw hydration errors whenever the feature is flipped. Images and more details in 🧵

Next.js hydration issues with feature flags can be tricky. On first glance, I'm not sure exactly where the mismatch is occurring, but I did want to share our Next.js pages example repo, which includes best practices for integrating GB with Next.js and the pages router: https://github.com/growthbook/examples/tree/main/next-js-pages Lmk if you've already seen it and are still running into issues.

@strong-mouse-55694 Thanks for the response. I've gone through all of these examples, though unfortunately some of it quite out of date. Most of the code is deprecated in current Growthbook packages, as you can see in the attached images. For example the package is using

0.17.0

even though the latest version is

1.3.1

. For example when updating the packages (including growthbook, next, react, and react-dom), the Pure Serverside Rendering example no longer functions properly, and all of the pages have deprecation warnings. All that being said, I think I've worked out a possible way to use the Provider alongside static pages, though I need to give it some more thorough testing.

Thanks for letting me know. We also have a more up-to-date example with the app router that may be useful until we have a chance to update the pages examples: https://github.com/growthbook/examples/tree/main/next-js