Roadmap

[mjackson]

This issue is a high-level roadmap for all work on the 5.x branch. The goal is to provide:

• a transparent process for the priority of a given piece of work
• an expected release version

The goal is not to discuss specific release dates, though some of that may happen.

This list is by no means exhaustive and will change from time to time as new issues are opened and PRs are merged.

4.4 5.0

• No warnings in React 16's <StrictMode>
  • Stop using legacy context
  • Remove all usage of componentWill* methods
• Single-file builds
  • Add warnings for deprecated react-router-dom/Link-style imports (5bde02b)
  • Add warnings about using 2 different builds (Add a warning about using different builds #6361)
  • Make tree-shaking actually work as expected (Bundling packages into single files is preventing useful tree-shaking #6464)
• Fully automated releases from CI

5.1

• Add useParams, useLocation, useHistory, and useRouteMatch hooks (d6224d6)
• Add support for forwardRef in (b5528ed)
• Add support for functions in <Link to> and <NavLink to> (Feature request: 'to' property as a function in Link component #5331, Make Link and NavLink components accept "to" property as a function #5368)
• Add <Link component> API (Feature Request: <Link component> #5437)

5.1.1

• Fix issue with useParams reading from null object (fix(useParams): fix issue with useParams reading from null object #6940)
• Fix regression passing ref to functional components in React <= 16.2 (Breaking change between version 5.0.1 and 5.1.0 #6934)
• Fix regression passing empty string to matchPath (Regression: empty string paths no longer match #6941)

5.1.2

• Fix lingering <Link ref> error on React 15 (React Router v5.1.1 Link Breaks with React v15.6.2 #6954)

5.2

• Stop pushing to the history stack on link clicks when location is the same (Use replace instead of push on <Link> click when location is the same #5362)

Backlog

• Add TypeScript and Flow types
• Define scope of react-router-config
• Use Suspense to allow cancelling navigation when the user follows another <Link> and the first one is still fetching- [ ] Add focus management APIs (SPA Accessibility - focus not reset when route changed #5210, Add <Focus> component to react-router-dom #6449, Add useFocus() hook to react-router-dom #6454)
• Isolate build artifacts to a single build directory
• Add a build for react-router-native so we can e.g. exclude __DEV__ code like we do in other package builds
• Move react-router-dom to react-router/dom to avoid context mismatch issues (react-router-dom -> react-router/dom #6755)