If you are using a Linux operating system and see an error similar to: ENOSPC: System limit for number of file watchers reached, you can fix the issue by increasing the fs.inotify.max_user_watches setting of your operating system. If none of these solutions help please leave a comment in this thread. This ensures that the next time you run npm start, the watcher uses the polling mode, as necessary inside a VM. env file in your project directory if it doesn’t exist, and add CHOKIDAR_USEPOLLING=true to it. If the project runs inside a virtual machine such as (a Vagrant provisioned) VirtualBox, create an.On Linux and macOS, you might need to tweak system settings to allow more watchers.If your project path contains parentheses, try moving the project to a path without them.Follow the instructions in “Adjusting Your Text Editor”. Some editors like Vim and IntelliJ have a “safe write” feature that currently breaks the watcher.If the watcher doesn’t see a file called index.js and you’re referencing it by the folder name, you need to restart the watcher due to a webpack bug.

If your project is in a Dropbox folder, try moving it out.TypeScript will show errors on any of your source files, but webpack only reloads your files if they are directly or indirectly imported by one of your entrypoints. Check that your file is imported by your entrypoint.If this doesn’t happen, try one of the following workarounds: When you save a file while npm start is running, the browser should refresh with the updated code. Troubleshooting npm start doesn’t detect changes

Intellij reactjs