<h3 dir="auto">Which website or app were you using when the bug happened?</h3>
<p dir="auto">Please provide a link to the URL of the website (if it is public), a CodeSandbox (<a href="https://codesandbox.io/s/new" rel="nofollow">https://codesandbox.io/s/new</a>) example that reproduces the bug, or a project on GitHub that we can checkout and run locally.</p>
<h3 dir="auto">What were you doing on the website or app when the bug happened?</h3>
<p dir="auto">If possible, please describe how to reproduce this bug on the website or app mentioned above:</p>
<ol dir="auto">
<li>

</li>
<li>

</li>
<li>

</li>
</ol>



<h3 dir="auto">Generated information</h3>
<p dir="auto">DevTools version: 4.13.1-93782cfed2</p>
<p dir="auto">Call stack:<br>
at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:21499:43<br>
at bridge_Bridge.emit (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:19607:22)<br>
at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:19767:12<br>
at listener (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:37788:39)</p>
<p dir="auto">Component stack:<br>
(none)</p>
<p dir="auto">GitHub URL search query:<br>
<a href="https://api.github.com/search/issues?q=Cannot%20remove%20node%20%20because%20no%20matching%20node%20was%20found%20in%20the%20Store.%20in%3Atitle%20is%3Aissue%20is%3Aopen%20is%3Apublic%20label%3A%22Component%3A%20Developer%20Tools%22%20repo%3Afacebook%2Freact">https://api.github.com/search/issues?q=Cannot%20remove%20node%20%20because%20no%20matching%20node%20was%20found%20in%20the%20Store.%20in%3Atitle%20is%3Aissue%20is%3Aopen%20is%3Apublic%20label%3A%22Component%3A%20Developer%20Tools%22%20repo%3Afacebook%2Freact</a></p>
<h3 dir="auto">Edit: If you have issues but you did NOT upgrade to 18, or if you upgraded but get confusing errors from dependencies, the problem is likely that some library (incorrectly) specifies <code class="notranslate">@types/react</code> as a dependency with version <code class="notranslate">*</code> rather than an optional peer dependency. Find which library it is and file an issue for it. See <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1196695161" data-permission-text="Title is private" data-url="https://github.com/facebook/react/issues/24304" data-hovercard-type="issue" data-hovercard-url="/facebook/react/issues/24304/hovercard?comment_id=1094565891&amp;comment_type=issue_comment" href="https://github.com/facebook/react/issues/24304#issuecomment-1094565891">#24304 (comment)</a> for diagnostics and common workarounds.</h3>
<p dir="auto">A few hours ago, a major version of React types for Typescript was released.</p>
<p dir="auto">I have tried to test this right away to see if there are any changes that require adaptation in my own projects.</p>
<p dir="auto">Due to a very large number of users using React's type library (we use fundamental types like React.FC by the hundreds in our own projects), it's reasonable to question whether there's been a small mistake here.</p>
<p dir="auto">Specifically, the following type declaration still exists in the 18 release.</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="type PropsWithChildren&lt;P&gt; = P &amp; { children?: ReactNode | undefined };"><pre class="notranslate"><code class="notranslate">type PropsWithChildren&lt;P&gt; = P &amp; { children?: ReactNode | undefined };
</code></pre></div>
<p dir="auto">However, this is no longer used in the library, at least not when looking at the diff<br>
<a class="commit-link" data-hovercard-type="commit" data-hovercard-url="https://github.com/DefinitelyTyped/DefinitelyTyped/commit/55dc209ceb6dbcd59c4c68cc8dfb77faadd9de12/hovercard" href="https://github.com/DefinitelyTyped/DefinitelyTyped/commit/55dc209ceb6dbcd59c4c68cc8dfb77faadd9de12">DefinitelyTyped/DefinitelyTyped@<tt>55dc209</tt></a></p>
<p dir="auto">A quick search on Github yields millions of hits that use the type alias React.FC to the actual type React.FunctionalComponent.</p>
<p dir="auto">Before</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="interface FunctionComponent&lt;P = {}&gt; {
      (props: PropsWithChildren&lt;P&gt;, context?: any): ReactElement&lt;any, any&gt; | null;
      ...
}"><pre class="notranslate"><code class="notranslate">interface FunctionComponent&lt;P = {}&gt; {
      (props: PropsWithChildren&lt;P&gt;, context?: any): ReactElement&lt;any, any&gt; | null;
      ...
}
</code></pre></div>
<p dir="auto">Now</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="interface FunctionComponent&lt;P = {}&gt; {
      (props: P, context?: any): ReactElement&lt;any, any&gt; | null;
}"><pre class="notranslate"><code class="notranslate">interface FunctionComponent&lt;P = {}&gt; {
      (props: P, context?: any): ReactElement&lt;any, any&gt; | null;
}
</code></pre></div>
<p dir="auto">I think matching very, very many places in a single project doesn't seem to do justice to the change made; always the property children?: ReactNode to be redefined is definitely too much effort.</p>
<p dir="auto"><strong>Positions at which PropsWithChildren were used before</strong></p>
<ul dir="auto">
<li>FunctionComponent, as shown in the example</li>
<li>ForwardRefRenderFunction,</li>
<li>und das Funktions-Interface propsAreEqual von memo</li>
</ul>
<p dir="auto">Thx!</p>