link tag inside browserrouter changes only the url, but doesn't render the component

If you use are using React Router 5.3.x, check whether it is 5.3.3 in your package.json file. If you use are using React Router 5.3.x, check whether it is 5.3.3 in your package.json file. If it is not 5.3.3 uninstall the last version then install the bug-free version which has been resolved by John and updated in version 5.3.3. If it is not 5.3.3 uninstall the last version then install the bug-free version which has been resolved by John and updated in version 5.3.3.

This is our Splunktool team suggestion ✌, we tried and its working fine

<BrowserRouter>
   <React.StrictMode>...</React.StrictMode>
</BrowserRouter>

Revert back to React 17 (or React 17 syntax) and fix up the index.js file.

import { StrictMode } from "react";
import ReactDOM from "react-dom";

import App from "./App";

ReactDOM.render(
  <StrictMode>
    <App />
  </StrictMode>,
  document.getElementById("root")
);

Make the React.StrictMode component a child/descendent of the router component. Comment.

Replace:

<React.StrictMode>
   ...
   <BrowserRouter>
      ...
   </BrowserRouter>
</React.StrictMode>

Upgrade to react-router-dom@6 and fix up the routes.

const App = () => {
  return (
    <Router>
      <Routes>
        <Route path="/" element={<Home />} />
        <Route path="/movies" element={<Home type="movies" />} />
        <Route path="/series" element={<Home type="series" />} />
        <Route path="/watch" element={<Watch />} />
      </Routes>
    </Router>
  );
}

React has launched its StrictMode in its latest update. you can see it in an index.js file

const root = ReactDOM.createRoot(document.getElementById('root'));
root.render(
<React.StrictMode>
   <App />
</React.StrictMode>
);

Suggestion : 2

set up the connected-react-router as doc. but it only update the url rather than the location object when yield put(push(/somewhere)) in saga. so it won’t re-render the component. try to resolve this via Update Blockingsection in react-router but it works fine outside the redux-saga. which means the push method from connected-react-router doesn’t work as expected. Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

I had the same problem and resolved it for some days. Finally, I found no history specified in tag <Router> and Router is BrowserRouter. I change it to <Router history={history}> (Router is default, not BrowserRouter) and the history is shared with router reducer. Code as below:

history.tsx

import {
   createBrowserHistory
} from 'history';
export default createBrowserHistory();

store.tsx

import {
   routerMiddleware
} from 'connected-react-router';

import history from './history';
import {
   createRootReducer
} from './reducer';
const appRootReducer = createRootReducer(history);
const appRouterMiddleware = routerMiddleware(history);
//...

!App.tsx

//...
import { BrowserRouter as Router } from 'react-router-dom';
class AppComponent extends React.Component {
    render() {
        return (
              <Router>
                    <main>{renderRoutes(routes)}</main>
              </Router>
        );
    }
}

Suggestion : 3

This code changes the URL but doesn't do anything for the UI. We would need to write some more code that changed some state somewhere to get the UI to change to the contact page. The trouble is, the browser doesn't give us a way to "listen to the URL" and subscribe to changes like this. With client side routing, developers are able to manipulate the browser history stack programmatically. For example, we can write some code like this to change the URL without the browsers default behavior of making a request to the server: React Router isn't just about matching a url to a function or component: it's about building a full user interface that maps to the URL, so it might have more concepts in it than you're used to. We'll go into detail on the three main jobs of React Router:

1._

<a
  href="/contact"
  onClick={(event) => {
    // stop the browser from changing the URL and requesting the new document
    event.preventDefault();
    // push an entry into the browser history stack and change the URL
    window.history.pushState({}, undefined, "/contact");
  }}
/>

2._

window.addEventListener("popstate", () => {
   // URL changed!
});

3._

let history = createBrowserHistory();
history.listen(({
   location,
   action
}) => {
   // this is called whenever new locations come in
   // the action is POP, PUSH, or REPLACE
});

5._

{
   pathname: "/bbq/pig-pickins",
   search: "?campaign=instagram",
   hash: "#menu",
   state: null,
   key: "aefz24ie"
}

6._

location.pathname + location.search + location.hash;
// /bbq/pig-pickins?campaign=instagram#menu

Suggestion : 4

Now, let's update the src/index.js page and import About from the file we've just created. Within the <BrowserRouter> tag, we'll define our routes and components associated with them: We've imported the <BrowserRouter> here, and we'd wrapped our entire application around it. We'd also selected App.js as the component for our home page (under the / endpoint), and About.js as the component for the /about page. The react-router-dom package makes it simple to create new routes. To begin, you wrap the entire application with the <BrowserRouter> tag. We do this to gain access to the browser's history object. Then you define your router links, as well as the components that will be used for each route.

Let's start out by creating a simple React application via the command line:

$ npx create - react - app router - sample

Once created, let's move into the project's directory, and start the application:

$ cd router - sample
$ npm start

As usual, installing a package using npm is as simple as running a single command:

$ npm install react - router - dom

5._

import { render } from "react-dom";
import { BrowserRouter, Routes, Route } from "react-router-dom";
import App from "./App";
import About from "./About";

render(
  <BrowserRouter>
    <Routes>
      <Route path="/" element={<App />} />
      <Route path="about" element={<About />} />
    </Routes>
  </BrowserRouter>,
  document.getElementById("root")
);

Finally, let's adapt the App.js file, which will, again, be the main entry point for the application and serve our home page:

import { Link } from "react-router-dom";

function App() {
  return (
    <div className="App">
      <h1>Welcome to my react app!</h1>
      <p>
        Lorem ipsum dolor sit amet consectetur adipisicing elit. Accusamus,
        pariatur?
      </p>
      <br />
      <Link to="/about">About Page</Link>
    </div>
  );
}

export default App;

Suggestion : 5

Also, the Route component offers two different props to link components: component and render, but it’s possible to offer one element prop as the Suspense API does. Moreover, for defining your routes with JavaScript objects in v5, you have to use the separate react-router-config package. We then supply the component to be rendered to the Route component as element props. We can also supply custom props to the components in each route we wish to render. This works well, however, we cannot pass props to the rendered component. The second is to pass in the component as a child of the Route component:

Look at the following example that demonstrates the ranking problem in the v5’s routing algorithm:

The correct way: Here, /games will render the Games component but not SelectedGame, because it does not have a parameter id. While /games/:id will render only the SelectedGame component:

<Router>
  <Route path="/games/:id" component={SelectedGame} />
  <Route path="/games" component={Games} />
</Router>

The incorrect way: Here, either /games or /games/:id will render the Games component:

<Router>
  <Route path="/games" component={Games} />
  <Route path="/games/:id" component={SelectedGame} />
</Router>

According to v5’s perspective, the second approach is incorrect, and developers need to use the exact prop or re-order (as in the first code snippet) to fix it. But, the v5 route ranking algorithm could be intelligent to identify the most suitable route without explicit ordering or exact usage.

For developing nested routes, developers had to use write more code with the useRouteMatch Hook, Route, and Switch components. For nested routes, developers had to find the entire route because there is no relative route handling in v5:

// ----
<Switch>
  <Route path="/dashboard" component={Dashboard} />
</Switch>;
// ----

function Dashboard() {
  const { path } = useRouteMatch();
  return (
    <div>
      <h1>Dashboard</h1>
      <Switch>
        <Route path={`${path}/charts`} component={Charts} />
      </Switch>
    </div>
  );
}

Next, run the following command to initiate an upgrade:

npm install[email protected]
#-- - or-- -
yarn install[email protected]

First, open a terminal in a project directory where React Router isn’t installed. To install a specific version of React Router, run the following:

npm install[email protected][VERSION_TO_BE_INSTALLED]

Suggestion : 6

Link tag inside BrowserRouter changes only the URL, but doesn't render the component React Router changes the URL but doesn't render the components React router Link changes URL, but doesn't render the component React Link tag changes the url but doesnt render the component

React has launched its StrictMode in its latest update. you can see it in an index.js file

const root = ReactDOM.createRoot(document.getElementById('root'));
root.render(
<React.StrictMode>
   <App />
</React.StrictMode>
);

So here your React Router is in the child component. And we have to make it a parent component.

const root = ReactDOM.createRoot(document.getElementById('root'));
root.render(
<BrowserRouter>
   <React.StrictMode>
      <App />
   </React.StrictMode>
</BrowserRouter>
);

Remove the Strict mode from the index.js file

const root = ReactDOM.createRoot(document.getElementById('root'));
root.render(
<BrowserRouter>
   <App />
</BrowserRouter>
);

Make the React.StrictMode component a child/descendent of the router component. Comment.

Replace:

<React.StrictMode>
   ...
   <BrowserRouter>
      ...
   </BrowserRouter>
</React.StrictMode>

with:

<BrowserRouter>
   <React.StrictMode>
      ...
   </React.StrictMode>
</BrowserRouter>