chore(deps): update dependency react-hot-loader to v4.13.1

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
react-hot-loader	4.12.20 -> 4.13.1

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

gaearon/react-hot-loader (react-hot-loader)

v4.13.1

Compare Source

v4.13.0

Compare Source

Bug Fixes

• tailUpdate might be blocked by a PureComponent (#​1448) (e44103a)
• when module.hot is not truthy (#​1451) (ec3447f)

Features

• support React 17 (#​1557) (c05396b), closes #​1425

4.12.21 (2020-04-30)

Bug Fixes

• add peerDependenciesMeta in package.json (#​1433)

4.12.20 (2020-03-14)

Bug Fixes

• patch support for react-dom 16.13 (#​1428) (5475fe7)

4.12.19 (2020-01-22)

Bug Fixes

• don't record signatures of local hooks, fixes #​1412 (#​1413) (c159844)

4.12.18 (2019-11-16)

Bug Fixes

• (regression) hook order change is causing React error, fixes #​1393 (6707b4b)
• production babel plugin might perform eager replacement, fixes #​1388 (b94adb3)

4.12.17 (2019-11-12)

Bug Fixes

• move @​types/react from to peer dependencies, fixes #​1391 (5ab2cab)

4.12.16 (2019-11-06)

Bug Fixes

• dont write to elementType if it is not defined, fixes #​1357 (1072303)
• explain why RHL could not be activated, fixes #​1362 (9561d66)
• more @​types/react to dependencies, fixes #​1359 (af42c1a)
• use logger.warn instead of console to report tail update, fixes #​1386 (fbc890a)

v4.12.21

Compare Source

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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 was generated by Mend Renovate. View the repository job log.

[microsvc-bot]

Hi @renovate[bot]. Thanks for your PR.

I'm waiting for a CloudNativeEntrepreneur member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository.

[microsvc-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please assign patrickleet
You can assign the PR to them by writing /assign @patrickleet in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment