From d4299e058e4dff78326b62c00f923bfced2d77d8 Mon Sep 17 00:00:00 2001
From: "github-actions[bot]"
 <41898282+github-actions[bot]@users.noreply.github.com>
Date: Fri, 19 Jun 2026 11:00:00 +0000
Subject: [PATCH] RELEASING: Releasing 1 package(s)

Releases:
  react-router-devtools@6.2.2

[skip ci]
---
 .changeset/vite-node-dependency-rr8-vite8.md | 7 -------
 packages/react-router-devtools/CHANGELOG.md  | 8 ++++++++
 packages/react-router-devtools/package.json  | 6 ++++--
 test-apps/react-router-vite/package.json     | 2 +-
 4 files changed, 13 insertions(+), 10 deletions(-)
 delete mode 100644 .changeset/vite-node-dependency-rr8-vite8.md

diff --git a/.changeset/vite-node-dependency-rr8-vite8.md b/.changeset/vite-node-dependency-rr8-vite8.md
deleted file mode 100644
index 7844a4d..0000000
--- a/.changeset/vite-node-dependency-rr8-vite8.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-"react-router-devtools": patch
----
-
-Fix `Cannot find package 'vite-node'` (#261) and support React Router 8 / Vite 8.
-
-`vite-node` is imported at runtime by the Vite plugin but was only declared as a `devDependency`, so consumers relied on it being a phantom dependency of `@react-router/dev@7`. React Router 8 dropped `vite-node` from its dependencies, which broke resolution for any project on RR8. `vite-node` is now a real `dependency` (`^5.0.0 || ^6.0.0`, covering both Vite 7 and Vite 8), and the `vite` peer range was tidied to `>=5.0.0` so it explicitly admits Vite 8 alongside React Router's existing `>=7.0.0` peer range (which already admits v8).
diff --git a/packages/react-router-devtools/CHANGELOG.md b/packages/react-router-devtools/CHANGELOG.md
index b4c3f02..593cd16 100644
--- a/packages/react-router-devtools/CHANGELOG.md
+++ b/packages/react-router-devtools/CHANGELOG.md
@@ -1,5 +1,13 @@
 # react-router-devtools
 
+## 6.2.2
+
+### Patch Changes
+
+- aae92e4: Fix `Cannot find package 'vite-node'` (#261) and support React Router 8 / Vite 8.
+
+  `vite-node` is imported at runtime by the Vite plugin but was only declared as a `devDependency`, so consumers relied on it being a phantom dependency of `@react-router/dev@7`. React Router 8 dropped `vite-node` from its dependencies, which broke resolution for any project on RR8. `vite-node` is now a real `dependency` (`^5.0.0 || ^6.0.0`, covering both Vite 7 and Vite 8), and the `vite` peer range was tidied to `>=5.0.0` so it explicitly admits Vite 8 alongside React Router's existing `>=7.0.0` peer range (which already admits v8).
+
 ## 6.2.1
 
 ### Patch Changes
diff --git a/packages/react-router-devtools/package.json b/packages/react-router-devtools/package.json
index ec17271..e250882 100644
--- a/packages/react-router-devtools/package.json
+++ b/packages/react-router-devtools/package.json
@@ -2,7 +2,7 @@
 	"name": "react-router-devtools",
 	"description": "Devtools for React Router - debug, trace, find hydration errors, catch bugs and inspect server/client data with react-router-devtools",
 	"author": "Alem Tuzlak",
-	"version": "6.2.1",
+	"version": "6.2.2",
 	"license": "MIT",
 	"keywords": [
 		"react-router",
@@ -55,7 +55,9 @@
 			"default": "./dist/server.js"
 		}
 	},
-	"files": ["dist"],
+	"files": [
+		"dist"
+	],
 	"repository": {
 		"type": "git",
 		"url": "git+https://github.com/code-forge-io/react-router-devtools.git"
diff --git a/test-apps/react-router-vite/package.json b/test-apps/react-router-vite/package.json
index fcf7c51..851c76c 100644
--- a/test-apps/react-router-vite/package.json
+++ b/test-apps/react-router-vite/package.json
@@ -23,7 +23,7 @@
     "@types/react": "^19.2.2",
     "@types/react-dom": "^19.2.2",
     "eslint": "^9.19.0",
-    "react-router-devtools": "^6.2.1",
+    "react-router-devtools": "^6.2.2",
     "typescript": "^5.9.3",
     "vite": "^7.2.2",
     "vite-plugin-inspect": "^10.1.0",