We have a Next.js site that currently is mostly statically rendered at build-time, and with an already fairly complex routing structure and proxy file, we're not interested in introducing more complexity via the precompute method this library provides.

Now that Next.js v16 is out and supports cache components (previously known as partial pre-rendering or PPR), it would be nice to have support for this alternate method of fetching flags in a static route.

We're considering loading flags on the client side at this time, as we can't see any functional difference to the end-user if an element pops into view via the server or a client fetch, aside from the fact that the server now has extra work to do, more costs for us etc. However this library, at least the Next.js adaptor, does not support the client side at all by default, which feels like a significant omission, especially before cache components were promoted to stable.