fix(deps): update dependency react-router-dom to v5

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
react-router-dom	dependencies	major	^4.3.1 -> ^5.2.0

---

Release Notes

ReactTraining/react-router

v5.2.0

Compare Source

This release includes a notable performance boost by separating the "Router" context from the "History" context internally. We also allow every element type for Link's component prop and support a sensitive prop on NavLink for control over case sensitive matching.

Enjoy!

Changes

• Add sensitive prop on NavLink (#​7251 by @​caseywebdev)
• Fix Link component prop type check (#​7276 by @​ypyakymiv)
• Update mini-create-react-context (#​7288 by @​patricksmms)
• Separate history to its own context (#​7103 by @​illuminist)

v5.1.2

Compare Source

List of commits

Bugfixes

• Fix lingering <Link ref> error on React 15 (#​6954)

v5.1.1

Compare Source

List of commits

Bugfixes

• Fix issue with useParams reading from null object (#​6940)
• Fix regression passing ref to functional components in React <= 16.2 (#​6934)
• Fix regression passing empty string to matchPath (#​6941)

v5.1.0

Compare Source

Read the blog post

List of commits

Features

• Add useParams, useLocation, useHistory, and useRouteMatch hooks (d6224d6)
• Add support for forwardRef in <Link> (b5528ed)
• Add support for functions in <Link to> and <NavLink to> (#​5331, #​5368)
• Add <Link component> API (#​5437)

Bugfixes

• Don't render <Route children> elements when the <Route> does not match (9665659)

v5.0.1

Compare Source

Changes

Updates

• Reduced component depth in withRouter() HOC. (10d78bb)
• Changed misleading warning when withRouter is used outside a Router (10d78bb)
• Reduced install size and bundle size by switching to mini-create-react-context (992af48)

Bugfixes

• Fixed display name for router context consumer and provider (6a99c93)
• Fixed infinite loop caused by Redirect in some scenarios (017f692 and 2ce1d32)
• Fixed license issue for react context polyfill (f9849c8, then 992af48)
• Fixed Redirect throwing an exception in StaticRouter without context (3ccbd19)
• Fixed regression in matchPath that caused an exception for empty paths (7bd1407)
• Fixed page reload when an exception was thrown in Link onClick (82ce94c)
• Fixed warning about createRef or useRef values in wrappedComponentRef when using withRouter() (56c829b)
• Fixed withRouter() wrapped component inside NavLink not working properly (a38ef04)
• Fixed CJS build - previously, incorrect exports were emitted (caa9950)

Thanks to @​StringEpsilon for putting this list together. Enjoy!

v5.0.0

Compare Source

Note: While this does have a major version bump, it is actually a minor release. We screwed up some of the dependency version selection in 4.3.1, which necessitated a major bump. See this blog post for details.

⚠️ Upgrade Warning ⚠️

Please ensure you have upgraded both react-router and react-router-dom (react-router-native for RN users) to the exact same version. If different versions of those two packages are in your application, you will get errors when using <Link> and other react-router-dom-specific components. You can ensure you have the correct versions of both packages in your app using npm ls react-router react-router-dom.

Breaking Changes

• Since the old context API is no longer used, any access to the old context will fail. Use of the react router context is not supported, please use withRouter() or a <Route/> instead.
• Due to the new context API, mixing of imports will now result in an exception:

// Be careful, this won't work anymore!
import BrowserRouter from 'react-router-dom/BrowserRouter';
import { Route } from 'react-router-dom';

<BrowserRouter>
  <Route />
</BrowserRouter>

Refactor as follows:

// These are both from the same build and use the same context object
// so there won't be a mismatch :)
import { BrowserRouter, Route } from 'react-router-dom';

• In development mode, we now throw an error when using 2 different builds (see b2c6fa0), i.E. combining CJS imports with ESM imports.

New Features

• <Route /> now supports an array of paths - #​5889 (thanks @​baronswindle)

<Route path={["/BigApple", "/NYC", "NewYork"]} component={NewYork} />

Full Changelog

• <Route /> now supports multiple child nodes when using react >= 16.0.
• Migrated to new react context API, with a polyfill for react versions < 16.2
• Removed deprecated lifecycle methods componentWillMount and componentWillReceiveProps
• Introduced more warnings in development builds
• Changed build-process to rollup:
  • Smaller build size
  • Package now includes pre-minified files
  • Package now consists of single-file builds that include all modules.
• Upgraded to history 4.9.0
• Per file imports are deprecated and will be removed in a future major version. For now, a warning will be logged.
• Made sure that react router conforms to react <StrictMode/>
• Fixed <Link /> not working properly with target="_self" - #​6138 (thanks @​ericyang89)
• Fixed prop-type warning when using forwardRef - #​6417 (thanks @​frehner and @​eXon)
• Added support for createRef in - #​6567 (thanks @​gcangussu)
• Removed use of eval in development to be compliant with unsafe-eval CSP - #​6611
• Migrated to babel-preset-env
• Improved testing infrastructure to improve developer workflow
• Several docs improvements - #​6410 (thanks @​justsml)

---

Renovate configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻️ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by WhiteSource Renovate. View repository job log here.