From ac3b8b6a1a7fc21be0ae82e7b1c9c08bfc9d2de4 Mon Sep 17 00:00:00 2001
From: blam <ben@blam.sh>
Date: Tue, 30 Aug 2022 11:11:04 +0200
Subject: [PATCH] chore: updating docs for `Navigate` component
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Co-authored-by: Patrik Oldsberg <poldsberg@gmail.com>
Co-authored-by: Fredrik Adelöw <freben@gmail.com>
Co-authored-by: Johan Haals <johan.haals@gmail.com>
Signed-off-by: blam <ben@blam.sh>
---
 docs/tutorials/react-router-stable-migration.md | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/docs/tutorials/react-router-stable-migration.md b/docs/tutorials/react-router-stable-migration.md
index 441d9964a9..9636345116 100644
--- a/docs/tutorials/react-router-stable-migration.md
+++ b/docs/tutorials/react-router-stable-migration.md
@@ -172,6 +172,15 @@ It's crucial that you update to `RequirePermission` at the same time as you upda
      />
 ```
 
+### `<Navigate />` component
+
+When migrating over to React Router v6 stable, you might also see browser console warnings for the `Navigate` component. This will need to be wrapped up in a `Route` component with the `Navigate` component in the `element` prop.
+
+```diff
+- <Navigate key="/" to="catalog" />
++ <Route path="/" element={<Navigate to="/catalog" />} />
+```
+
 ### `NavLink`
 
 The `NavLink` component no longer has the `activeClassName` and `activeStyle` props. Instead, the `className` and `style` props accept a callback that receives a boolean indicating whether the link is active.