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.
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.
@alex.trost But itβs written that you support adapter-universal, meaning we could at least setup slice machine without issue. Iβve been trying to setup a tanstack start project, I donβt need all @prismicio/next code, i just want to start the slice machine.
Whatβs wrong ?
~/dev-workspace/pro/website (main*) Β» bunx -bun @slicemachine/init 1 β΅ screamz@ScreamZ-Macbook
Slice Machine β Initializing
βΉ We collect telemetry data to improve user experience.
Learn more: https://prismic.dev/slice-machine/telemetry
β Detected framework universal (no framework) and package manager npm
β Began core dependencies installation with npm ... (running in background)
β Logging in to Prismic...
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
* * Press any key to open the browser to login...
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
Command failed with exit code 1: npm i -D slice-machine-ui@latest @slicemachine/adapter-universal@latest --color=always --loglevel=info
npm info using npm@11.6.2
npm info using node@v25.2.1
npm http cache https://registry.npmjs.org/slice-machine-ui 28ms (cache hit)
npm notice Access token expired or revoked. Please try logging in again.
npm http fetch GET 404 https://registry.npmjs.org/@slicemachine%2fadapter-universal 137ms (cache skip)
npm notice Access token expired or revoked. Please try logging in again.
npm http fetch GET 404 https://registry.npmjs.org/@slicemachine%2fadapter-universal 48ms (cache skip)
npm error code E404
npm error 404 Not Found - GET https://registry.npmjs.org/@slicemachine%2fadapter-universal - Not found
npm error 404
npm error 404 The requested resource '@slicemachine/adapter-universal@latest' could not be found or you do not have permission to access it.
npm error 404
npm error 404 Note that you can also install from a
npm error 404 tarball, folder, http url, or git url.
npm error A complete log of this run can be found in: /Users/screamz/.npm/_logs/2026-01-14T20_31_09_467Z-debug-0.log
β Dependency installation failed, try again with: