<p dir="auto">When I console.log(), the Chrome console gives the log but instead of showing the file and line number it just says react_devtools_backend.js:4049. How do I get the console to show the file and line number when I console.log()?</p>
<p dir="auto">in my browser console, log info go wrong, it should show real console.log file and correct line info, but now it always show "react_devtools_backend.js: 4049", link to source code show warning:<br>
"Warning: componentWillReceiveProps has been renamed, and is not recommended for use. See <a href="https://fb.me/react-unsafe-component-lifecycles" rel="nofollow">https://fb.me/react-unsafe-component-lifecycles</a> for details.</p>
<ul dir="auto">
<li>Move data fetching code or side effects to componentDidUpdate.</li>
<li>If you're updating state whenever props change, refactor your code to use memoization techniques or move it to static getDerivedStateFromProps. Learn more at: <a href="https://fb.me/react-derived-state" rel="nofollow">https://fb.me/react-derived-state</a></li>
<li>Rename componentWillReceiveProps to UNSAFE_componentWillReceiveProps to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run <code class="notranslate">npx react-codemod rename-unsafe-lifecycles</code> in your project source folder.<br>
Please update the following components: %s"<br>
when i disable react developer tools, it goes correctly. but it goes wrong in 4.18.0 react developer tools. and my colleagues' chrome with react developer tools 4.17.0 is right</li>
</ul>
<h3 dir="auto">Note from maintainers: <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="989655954" data-permission-text="Title is private" data-url="https://github.com/facebook/react/issues/22257" data-hovercard-type="issue" data-hovercard-url="/facebook/react/issues/22257/hovercard?comment_id=916174962&amp;comment_type=issue_comment" href="https://github.com/facebook/react/issues/22257#issuecomment-916174962">#22257 (comment)</a> is a workaround until this is fixed in React DevTools</h3>