BrowserRouter in React — React Technical Interview Questions & Answers
BrowserRouter in React
BrowserRouter in React
- BrowserRouter uses the real path: /about. HashRouter uses /#/about. Real paths look better and help SEO a bit, but the server must return index.html for unknown paths — otherwise refresh on /about is a 404. That’s the deploy trap.
- Vite/Netlify/nginx SPA fallback is the fix. Mention it. Don’t only recite ‘BrowserRouter is better’.
- BrowserRouter in React — output: real URL vs hash vs deploy trap. Refresh on /about must not 404.
URL /about
│ BrowserRouter
▼
<Route> → About
│ Link
▼
no full reloadTechnical Interview Tip: Real URL + refresh 404 trap.
Code Examples for BrowserRouter in React
Example
// BrowserRouter
console.log("BrowserRouter uses /about in the address bar");
console.log("HashRouter would use /#/about");
console.log("Deploy: serve index.html for unknown paths");
BrowserRouter in React — output: real URL vs hash vs deploy trap. Refresh on /about must not 404.
How to Explain BrowserRouter in React to an Interviewer
Explain BrowserRouter as if you are teaching a junior — definition, then one tiny UI.
HTML5 history URLs. server fallback to index.html.
What does the example show on screen (or print), and what does that prove?
BrowserRouter in React — output: real URL vs hash vs deploy trap
What mistake do freshers make with BrowserRouter?
HashRouter if you can’t configure the server.