Redirecting alone is done via the Navigate component with the replace prop specified.

<Navigate replace to="/" />

If you want to replicate RRDv5’s Redirect component redirecting from a path then you need to combine with a Route.

<Route path="/somePath" element={<Navigate replace to="/" />} />

• Navigate
• Routes
• Route

If you aren’t server rendering your app you can still redirect on the initial render in the client like this:

import { Routes, Route, Navigate } from "react-router-dom";

    function App() {
      return (
        <Routes>
          <Route path="/home" element={<Home />} />
          <Route path="/" element={<Navigate replace to="/home" />} />
        </Routes>
      );
    }

In the above example, when someone visits /, they will automatically be redirected to /home, same as before.

Please note however that this won’t work when server rendering because the navigation happens in a React.useEffect().

Have a look at Redirects in React Router v6 for some deeper details.

Redirecting in react-router-dom v6 is done with the <Navigate> Component with replace props.

Step 1:

import { Navigate } from 'react-router-dom';

Step 2:

<Routes>
    <Route path='/' element={<Navigate replace to='/search' />} />
</Routes>

Here is what the react-router-dom teams said on the matter of redirects when that removed that API in v6: https://github.com/remix-run/react-router/blob/main/docs/upgrading/reach.md#redirect-redirectto-isredirect

If you want the application to direct you to the “Home” page when you type non-existent gibberish into the address bar, try specifying the path=”*” parameter.

<Routes> <Route path="*" element={<Navigate replace to="/Home"/>} /> </Routes>

In v6.2.*
Just add a Route with path to *

<Routes>
  <Route path="/" element={<App />}>
    <Route path="expenses" element={<Expenses />} />
   
    <Route
      path="*"
      element={
        <main style={{ padding: "1rem" }}>
          <p>There's nothing here!</p>
        </main>
      }
    />
  </Route>
</Routes>

Official Doc