fix: declare vite-node as a dependency + support React Router 8 / Vite 8 (#261)

[AlemTuzlak]

Summary

Fixes #261 — react-router-devtools failed with Error [ERR_MODULE_NOT_FOUND]: Cannot find package ''vite-node'' after upgrading a project to React Router 8.

Root cause

The Vite plugin imports vite-node at runtime (src/vite/node-server.ts) to execute react-router.config.ts and route files. vite-node is marked external in tsup.config.ts, so it stays a bare import vite-node/... in the published dist/index.js — it must be resolvable at the consumer. But it was declared only as a devDependency.

It worked on React Router 7 purely as a phantom dependency: @react-router/dev@7 declares vite-node as a real dependency, which pnpm hoisted so the devtools could resolve it. @react-router/dev@8 removed vite-node from its dependencies, so the phantom dependency disappeared and resolution broke for any project on RR8.

Changes

• Move vite-node to dependencies with range ^5.0.0 || ^6.0.0 (vite-node@5 → Vite 7, vite-node@6 → Vite 8). This is the actual fix — it remains external in tsup (correct; it resolves at the consumer).
• Tidy the vite peer range to >=5.0.0 (was >=5.0.0 || >=6.0.0). The react-router >=7.0.0 peer range already admits v8; both floors now explicitly cover React Router 8 + Vite 8.
• New example test-apps/react-router-v8-vite/ — a minimal RR8 + Vite 8 framework-mode app that wires the devtools plugin in by package name (not a relative dist/ path) so it exercises the real consumer resolution path, including the vite-node dependency.
• Single React version across the workspace — RR8 requires react >=19.2.7, and the workspace shares one linked react-router-devtools across all examples. Without a single React version, the devtools'' React subtree (TanStackDevtools) hit an Invalid hook call from a react/react-dom mismatch. Aligned react/react-dom/@types/* to ^19.2.7/^19.2.2 across the examples + docs and pinned react/react-dom via root pnpm.overrides.
• sherif: ignore the intentionally-divergent v8 example (-p react-router-v8-vite) so the RR7-vs-RR8 / Vite7-vs-Vite8 divergence doesn''t trip the dependency check.
• Added a changeset (patch).

Verification

• ✅ New RR8/Vite8 example: react-router dev boots with no vite-node error, page renders (HTTP 200), devtools instrumentation active; build and typecheck pass.
• ✅ Existing RR7/Vite7 examples (react-router-vite, custom-server) still build & typecheck.
• ✅ react-router-devtools package: typecheck clean, 377 unit tests pass.
• ✅ sherif and biome clean.

Notes

• The published-package fix is the vite-node dependency move + peer range; the pnpm.overrides and example version bumps are monorepo-dev concerns only (root package.json is private).
• In the monorepo, the shared devtools resolves vite-node@5, so the v8 example runs vite-node@5''s server against a Vite 8 dev server — verified working. A real single-version RR8 consumer would resolve vite-node@6.

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/react-router-devtools@262

commit: 57ea23b