title: how to ignore or fix a runtime error unique to chrome and next.js
body: <p>I'm using a boilerplate next.js template provided by this commmand:</p>
  <pre><code>npx create-next-app .
  </code></pre>
  <p>The error I get when I try to type anything on the chrome devtools console:</p>
  <pre><code>Unhandled Runtime Error
  EvalError: Possible side-effect in debug-evaluate
  </code></pre>
  <p>My question: Is there a way to ignore or completely fix this type of error?</p>
  <p>First: The supposed &quot;<a href="https://stackoverflow.com/questions/72396527/evalerror-possible-side-effect-in-debug-evaluate-in-next-js">duplicate solution</a>&quot; is a closed question with no accepted answer. The only response doesn't really offer a solution.</p>
  <p>What I have tried</p>
  <ul>
  <li>Tested on both Microsoft Edge and Mozilla Firefox. They don't seem to have this problem. My chrome version is: <code>Version 102.0.5005.63 (Official Build) (64-bit)</code>.</li>
  <li>Tested create-react-app and a normal js/html app and both don't seem to trigger errors. I'm concluding that this error is unique to the nextjs/chrome combo.</li>
  <li>Same problem happens on other windows computers. This means that this problem is possibly global</li>
  <li>Disabling the &quot;eager evaluation&quot; option in the chrome devtools seems to have solved the problem. I'm still looking for a solution that doesn't involve the removal of this feature.</li>
  </ul>