title: Chrome devtools not logging "undefined" anymore?
body: <p>So, since a few days, my <code>chrome developer tools</code>/<code>console</code> won't output <em>any</em> <code>undefined</code> errors or <code>Uncaught ReferenceError</code> in some cases.
  The script <em>just stops</em> without any indication, and I <em>don't</em> have <code>pause on exceptions</code> on, and there's <em>no</em> breakpoints.</p>
  
  <p>Trying to call an <code>undefined</code> function <code>foo()</code> for example:</p>
  
  <p><a href="https://i.stack.imgur.com/8u9pE.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/8u9pE.png" alt="enter image description here"></a></p>
  
  <p>I have the filter on <code>all</code> so I'm not filtering anything.</p>
  
  <p>I've reset the settings via <code>Settings-&gt;General-&gt;'Restore defaults and reload'</code></p>
  
  <p>I've tried disabling <em>all</em> extensions, but no difference.</p>
  
  <p>I've tried a new user in chrome, still nothing</p>
  
  <p>I've tried using <code>"use strict"</code> in my code, nothing.</p>
  
  <p>I'm pretty sure this has something to do with <code>reactjs</code>, where <code>foo()</code> is not defined anywhere, but try to call it like the above screenshot. I had the same issue inside <code>mixins</code>.</p>
  
  <p>Strangest thing is, that not all reactClasses have this problem. Also I've been through version 14.x to 14.7.</p>
  
  <p>I've even tried <strong>copying</strong> a reactClass/Component which <strong>does</strong> output an error <code>Uncaught ReferenceError</code> as I'm trying in the above screenshot, but just give it another name (ie assign to different variable and export as separate module). And you guessed it, then the above screenshot occurs, no error, <strong>For the same exact code</strong> ?</p>
  
  <p>I know, you're probably thinking I'm doing something terribly wrong, but how does a <strong>copy</strong> behave differently?</p>
  
  <p>I think the above image indicates that something very strange is happening here. There must be a logical explanation, but I can't find any.</p>
  
  <p>This is extremely frustrating, and I'm at a loss how to fix this/what the cause is.</p>
  
  <p>It also doesn't matter where I put <code>foo()</code>, whether it's in <code>render</code> or in <code>componentWillMount</code> or any other method. And the worst is, if it's in <code>componentDidMount</code> I don't even notice, except that the component doesn't react or update anymore.</p>
  
  <p>Upon further investigation it seems this problem only occurs on the <strong>first render</strong> of the whole component hierarchy...
  This is new to me, it's as if the initial render has to be flawless and otherwise it will just halt without informing the developer.</p>
  
  <p>On the upside, I now have to pay extra attention to the coherence of my code ;P. But truly, I can't really work like this.</p>