Is your feature request related to a problem? Please describe.
I have a client interested to switch from React client side rendering to Next.js static site generation. However, given that this library is written client-side, we cannot use React Server Components / Next.js App Router.
Describe alternatives you've considered
This library works fine if you stick to the old Next.js Pages Router. However, in that case its is not possible to leverage the best and latest features of React and Next.js. For example the new caching mechanism and full SSG that makes pages perform great on mobile, with Lighthouse scores comparable with Adobe EDS.
Additional context
I really hope this gets prioritized by Adobe, as not every client is open for switching to EDS and plain JS development duo to resource limitations and the fact that frontend devs are much more open to work with React/Next.js stack. I see this approach as a great alternative to EDS providing more flexibility.
Is your feature request related to a problem? Please describe. I have a client interested to switch from React client side rendering to Next.js static site generation. However, given that this library is written client-side, we cannot use React Server Components / Next.js App Router.
Describe the solution you'd like It would be great if we had support for editing React Server Components with AEM Standard Editor or Universal Editor. Competitor CMS systems already have support for visual editing/live preview of React Server Components. See for example https://www.storyblok.com/tp/add-a-headless-cms-to-next-js-13-in-5-minutes or https://www.contentful.com/blog/integrate-contentful-next-js-app-router/
Describe alternatives you've considered This library works fine if you stick to the old Next.js Pages Router. However, in that case its is not possible to leverage the best and latest features of React and Next.js. For example the new caching mechanism and full SSG that makes pages perform great on mobile, with Lighthouse scores comparable with Adobe EDS.
Additional context I really hope this gets prioritized by Adobe, as not every client is open for switching to EDS and plain JS development duo to resource limitations and the fact that frontend devs are much more open to work with React/Next.js stack. I see this approach as a great alternative to EDS providing more flexibility.