Unexpected prop type errors on first hot reload when using Context API

[edmorley]

Description

When using the new React Context API, the first hot reload results in seemingly invalid prop errors when using react-hot-loader.

Expected behavior

No additional prop type errors by using RHL.

Actual behavior

An unexpected prop type error shown (only) on the first hot reload (notifications is provided by the context):

Warning: Failed prop type: The prop `notifications` is marked as required in `NotificationsMenu`, but its value is `undefined`.
    in NotificationsMenu (at Notifications.jsx:43)
    in HotExportedApp (at src/index.jsx:6)

Environment

• react-hot-loader: v4.3.12
• node -v: v11.0.0
• npm -v: N/A (using yarn)
• yarn -v: 1.12.0
• OS: Windows 10
• Browser: this morning's Firefox Nightly (20181031223503)

Reproducible Demo

1. Clone https://github.com/edmorley/testcase-react-hot-loader-prop-type-errors
2. yarn
3. yarn start
4. In the browser tab that is then opened, open the devtools console
5. Edit src/App.jsx (eg adjust the text within the <div>)
6. Check the browser console for prop type errors

This testcase is derived from the implementation in mozilla/treeherder (mozilla/treeherder#4216 (comment)).

cc @camd.

[edmorley]

I've updated the testcase repository to RHL 4.6.1 - the issue still reproduces on the latest version.

[theKashey]

4.6.3 should solve the issue.

[edmorley]

Many thanks!