I’m evaluating Plasmic for a project migration and I’m really impressed with the platform overall. However, I’ve hit some limitations around Next.js App Router support that are blocking some key features I need to implement.
I’m trying to leverage React Server Components for better performance and implement view transitions for smooth page navigation. From what I can see, Plasmic’s App Router support is still limited, which is preventing me from using these newer Next.js features effectively.
A few questions: What’s the current state of full App Router support in Plasmic? Is there a timeline or roadmap for complete App Router compatibility? Are Server Components and view transitions on the radar for support? And are there any workarounds you’d recommend in the meantime?
I’d love to move forward with Plasmic, but these features are pretty critical for the stack I’m planning. Any insights into the development priorities here would be really helpful.
Thanks for your work on this platform - it’s genuinely exciting tech.
App router support is one of your main priorities now. We have a few SSR related issues to solve, and are working on providing better examples. Technically it is possible to use Plasmic with app router now, although the API is subject to change.
Are you building a loader project, or using codegen?
Regarding view transitions, I’ll ping the team to see if it’s on the radar.
I’m using the loader approach with the catch-all route pattern and getStaticProps/ISR — the standard Pages Router setup.
I’m fine staying on Pages Router for now since it works well. Happy to test and give feedback once App Router support is more stable.
I’m curious about the architectural direction for data fetching with RSCs. The current extractPlasmicQueryData approach won’t work in an RSC context since client components can’t be pre-rendered there. I saw the @plasmicapp/nextjs-app-router package that hits the dev server’s SSR endpoint as a workaround, but that feels temporary.
Are you planning to move toward components that can declare data needs statically, or will you refine the current SSR-roundtrip approach?
Is there a GitHub issue I can follow for App Router progress?
The current implementation looks like this, but it’s limited to data fetching at the page level. There is progress on implementing queries in components that will hopefully work out
@plasmicapp/nextjs-app-router was an experimental approach that isn’t used anymore. For data fetching in code components, we’ll probably end up with some way to register if/how it can be SSR’d.
Unfortunately we don’t have a great way to publicly track progress besides announcements on social media/Slack.
Would be cool if interested outsiders like me can see progress, and maybe even contribute. Would you guys consider making development branches public, or is that not desirable?
I’m in the same situation: evaluating Plasmic for a new project and lack of official, announced support for the NextJs app router is a major downside. Are there any updates on the timeline?
