<p dir="auto">Dan Abramov mentioned that Devtools v4 will be making <code class="notranslate">react-hot-loader</code> obsolete: <a href="https://twitter.com/dan_abramov/status/1144715740983046144?s=20" rel="nofollow">https://twitter.com/dan_abramov/status/1144715740983046144?s=20</a></p>
<blockquote>
<p dir="auto"><strong>Me:</strong><br>
I have this hook:<br>
<code class="notranslate">require("react-reconciler")(hostConfig).injectIntoDevTools(opts);</code><br>
But HMR has always worked completely without it. Is this now a new requirement?</p>
</blockquote>
<blockquote>
<p dir="auto"><strong>Dan:</strong><br>
Yes, that's what the new mechanism uses. The new mechanism doesn't need "react-hot-loader" so by the time you update, you'd want to remove that package. (It's pretty invasive)</p>
</blockquote>
<p dir="auto">I can't see any mention of HMR in the Devtools documentation, however; now that <code class="notranslate">react-hot-loader</code> has become obsolete (and with it, the <code class="notranslate">require("react-hot-loader/root").hot</code> method), how should we set up apps for HMR in:</p>
<ul dir="auto">
<li>React DOM apps</li>
<li>React Native apps</li>
<li>React custom renderer apps</li>
</ul>
<p dir="auto">I'd be particularly interested in a migration guide specifically for anyone who's already set up HMR via <code class="notranslate">react-hot-loader</code>.</p>
<p dir="auto">Also, for HMR, does it matter whether we're using the standalone Devtools or the browser-extension Devtools?</p>
<p dir="auto">Describe what you were doing when the bug occurred:</p>
<ol dir="auto">
<li>Was profiling component performance.</li>
</ol>
<hr>
<h2 dir="auto">Please do not remove the text below this line</h2>
<p dir="auto">DevTools version: 4.2.0-a8b8ffb89</p>
<p dir="auto">Call stack: at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:156567<br>
at Map.forEach ()<br>
at commitIndex (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:156513)<br>
at e.getRankedChartData (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:157036)<br>
at gl (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:314363)<br>
at fi (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:59263)<br>
at lc (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:103717)<br>
at kc (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:89467)<br>
at wc (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:89392)<br>
at pc (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:86341)</p>
<p dir="auto">Component stack: in gl<br>
in div<br>
in div<br>
in div<br>
in _o<br>
in Unknown<br>
in n<br>
in Unknown<br>
in div<br>
in div<br>
in zi<br>
in Ge<br>
in un<br>
in ba<br>
in Rc</p>