react-router
https://github.com/reacttraining/react-router
JavaScript
Declarative routing for React
Triage Issues!
When you volunteer to triage issues, you'll receive an email each day with a link to an open issue that needs help in this project. You'll also receive instructions on how to triage issues.
Triage Docs!
Receive a documented method or class from your favorite GitHub repos in your inbox every day. If you're really pro, receive undocumented methods or classes and supercharge your commit history.
JavaScript not yet supported3 Subscribers
Add a CodeTriage badge to react-router
Help out
- Issues
- [Docs]: Docs for shouldRevalidate make it sound like it is only for opting out
- [Bug]: `useLocation` out of sync with `history.location`, leads to potential renders of unmatched `Route`s
- [Bug]: Outlet component remounts in production when changing state above it
- Type inference
- [Bug]: useLocation value being null when 0 is set as the state value of useNavigate
- [Bug]: React router doesn't handle 'content://' URLs
- [Docs]: for useSearchParams, functional updates should be explained in more detail
- [Bug]: Getting "A router only supports one blocker at a time" warning when running your navigation-blocking example
- [Bug]: Navigation from '//' pathname does not work; path '*' is not matching the '//' page
- [Bug]: lazy loaded module error in nested router is catched only by the parent route with the * wildcard, not by the `errorElement` in the nested router
- Docs
- JavaScript not yet supported