title: React does not compile/build new files - (after a while!)
body: <p>Hi I am fairly new to React,</p>
  
  <p>And I am at that stage of trying to build my simple good for nothing single page application to learn about how things work.</p>
  
  <p>I am using Min 19, and IntelliJ Ultimate.</p>
  
  <p>I start on the terminal with <code>create-react-app new-app-7</code> and I run the application by <code>npm start</code> </p>
  
  <p>my <code>node version</code> command spits out this information at the moment.
  <code>npm version
  { 'new-app-7': '0.1.0',
    npm: '6.4.1',
    ares: '1.14.0',
    cldr: '32.0.1',
    http_parser: '2.7.1',
    icu: '60.2',
    modules: '57',
    nghttp2: '1.30.0',
    node: '8.10.0',
    openssl: '1.1.0g',
    tz: '2017c',
    unicode: '10.0',
    uv: '1.18.0',
    v8: '6.2.414.50',
    zlib: '1.2.11' }
  </code></p>
  
  <p>Everything works, I create/update a component, stuff happens in the "npm start" terminal window and changes are reflected on the browser. Everything is fan-damn-tastic so far.</p>
  
  <p>After some point the watcher (i don't know which one, it is the default one that comes with create-react-app and react-scripts I guess) stop detecting "new files" But it is not really an update issue, the newly generated files are completely ignored and not even compiled.</p>
  
  <p>For example I create
  Component1, Component2, Component3 all fine (very similar components with different text!) and suddenly everything stops working at Component4</p>
  
  <p>I create a completely new project <code>create-react-app new-app-8</code> and I can write code for a while normally Comp1, C2, C3, C4, C5 and it again does the same thing at a random point...</p>
  
  <p>Even if I stop the process and run <code>npm start</code> manually, the system is completely blind to the new file. I am doing intentional parse errors in this file and no complaints on the compile screen. When I try to import this component to a previously created one I get "Can't resolve" errors.</p>
  
  <p>Despite knowing that it is not a watching issue I installed nodemon, which correctly detects that a new file is created/changed and triggers npm start but again the file is not compiled.</p>
  
  <p>I am thinking there is some sort of cache somewhere that is bugging out after some duration?</p>
  
  <p>The linux mint is also in a vmware but I suppose that should not cause a problem.</p>
  
  <p>I tried googling the problem, thinking it should be a fairly common one but using keywords "watcher" "not compiling" etc diverts me to very wrong alleys.</p>
  
  <p>Anyone has any suggestions? or pointers?</p>
  
  <p>edit 1: tried this to no luck. <code>rm -rf node_modules/ &amp;&amp; npm install &amp;&amp; npm start -- --reset-cache</code></p>