-
| Hi, I noticed recently when debugging in our app, that sticking <React.StrictMode> <BrowserRouter> <Routes> <Route path="/" element={<App />}> <Route index element={<Home />} /> <Route path="/page-1" element={<Page1 />} /> <Route path="/page-2" element={<Page2 />} /> </Route> </Routes> </BrowserRouter> </React.StrictMode>Is there something I'm doing or haven't done properly with this setup? Thanks, |
Beta Was this translation helpful? Give feedback.
Answered by b-89 Apr 28, 2022
Replies: 1 comment
-
| So after some more digging, it appears that it's caused by supasate/connected-react-router#193 (comment) Not sure why when I tried googling the other day, I didn't notice this topic. It could be useful to mention this in the official documentation that this happens. |
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by b-89
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
So after some more digging, it appears that it's caused by
<React.StrictMode>.supasate/connected-react-router#193 (comment)
Not sure why when I tried googling the other day, I didn't notice this topic. It could be useful to mention this in the official documentation that this happens.