React create app hot reload is not always working on linux

I created a react application using create-react-app boilerplate, which seems to be very popular, hot reload some times updates when any of the files changes and some times not, seems like there is a minimum duration or something like that, I’m using Ubuntu, node version 7.0, the script in package.json is npm:'react-script start' what I am missing ?

  • forever does not start on server reboot
  • Installing a tar.gz on linux
  • How can I uninstall or upgrade my old node.js version?
  • Nodejs cpu profiling
  • Error: Could not locate the bindings file. Tried: #56
  • Can't find out where does a node.js app running and can't kill it
  • Geddy CLI closes on SSH drop
  • How to start a process that won't end when my ssh session ends?
  • “sh: line 1: Moved: command not found” installing npm with curl | sh
  • Node.js: Check if file is an symbolic link when iterating over directory with 'fs'
  • Syntax error: newline unexpected node.js rpm
  • NodeJs on Router via DD-WRT or OpenWRT?
  • 2 Solutions collect form web for “React create app hot reload is not always working on linux”

    When npm start doesn’t detect changes, below are the common troubleshooting steps provided in the create-react-app documentation – link.

    While an app is running with npm start and updating code in the editor should possibly refresh the borswer with the updated code.
    If this doesn’t happen, try one of the following workarounds:

    1. If the project files are directly synced to your local system from a cloud storage like Dropbox or Google Drive and your trying to run the app in them directly, try moving it out.
    2. Due to Webpack bug, you may need to restart the watcher. If the watcher doesn’t detect the index.js and you’re referencing it by the folder name.
    3. Safe write feature in editors like Vim and IntelliJ currently breaks the watcher. You will need to disable it.
    4. Due to Webpack watcher bug, projects with path contains parentheses causes issue, try moving the project to a path without them. .
    5. To allow more watchers in Linux and macOS, you might need to tweak system settings.
    6. If the project runs inside a virtual machine such as (a Vagrant provisioned) VirtualBox, create an .env file in your project directory if it doesn’t exist, and add CHOKIDAR_USEPOLLING=true to it. This ensures that the next time you run npm start, the watcher uses the polling mode, as necessary inside a VM.
    7. Could try increasing max_users_watches– link

    More references:

    • Issue Tracker 1
    • Toubleshooting webpack
    • Issue Tracker 2 – Webpack polling

    Try these:

    • Turn off safe write in your IDE
    • Increase max_user_watches
    • Your path should not have parentheses

    as last resort try to use this as your env variable:
    CHOKIDAR_USEPOLLING=true npm start


    Node.js is the Best Javascript runtime in the world.