Support for React Router

Prismic Administrative Support Features
, ,
1

Support for React Router (slicemachine adapter)

Issue that it solves:

Currently, teams using React Router (v7+) for modern web apps do not have an official way to integrate Slice Machine and Prismic slices in a structured, developer-friendly way.

Without an adapter:

  • Developers must manually wire up Prismic’s API client and handle route-based content fetching.
  • Slice previews, page modelling, and automatic type generation are not natively supported or error all the time using the nextjs adapter.
  • Teams miss out on the seamless slice development workflow (local simulation, custom types sync, previews) available in Next.js/Nuxt.js projects.

This limits the adoption of Prismic for projects using React Router or Remix-style SSR setups where React Router is the routing backbone.

Why It Matters

  • React Router v7 has become the go-to routing system for non-Next.js React apps, particularly in Vite, Remix, and SPA-to-MPA hybrid setups.
  • It reinforces Prismic’s “framework-agnostic” philosophy and broadens the ecosystem beyond opinionated meta-frameworks.
2

Hey @michealndo , thanks so much for the detailed post!

There are definitely some great frameworks that we don’t support yet, React Router being one of them. I definitely understand the pain points you’re experiencing trying to use Prismic with an unsupported framework. You miss out on so many features that it must be frustrating.

We aren’t currently expanding past the three we support, but we are keeping track of user interest to help shape those decisions when we do bring the next framework(s) on board. I’ll reply here if we decide to support react router, but for now it’s not on the roadmap.

1 Like