Meta tags:
description=npm start doesn’t detect changes;

Headings (most frequently used words):

npm, run, build, start, to, on, fails, troubleshooting, doesn, detect, changes, fail, due, watch, error, test, hangs, or, crashes, macos, sierra, exits, too, early, heroku, moment, js, locales, are, missing, minify,

Text of the page (most frequently used words):
the (39), you (30), your (18), npm (17), this (17), #moment (14), and (14), run (13), build (11), react (10), are (10), that (10), locale (9), can (8), system (8), watchman (8), doesn (7), with (7), project (7), start (6), import (6), try (6), facebook (5), locales (5), following (5), scripts (5), copy (5), need (5), running (5), create (5), app (5), file (5), watcher (5), github (4), fails (4), test (4), fail (4), error (4), only (4), help (4), sudo (4), sysctl (4), too (3), early (3), macos (3), due (3), page (3), using (3), modern (3), problem (3), because (3), them (3), inside (3), node_modules (3), will (3), for (3), have (3), imported (3), from (3), use (3), might (3), files (3), process (3), memory (3), issue (3), these (3), one (3), more (3), inotify (3), max_user_watches (3), linux (3), webpack (3), troubleshooting (3), started (2), docs (2), minify (2), missing (2), heroku (2), exits (2), hangs (2), crashes (2), sierra (2), watch (2), detect (2), changes (2), updated (2), likely (2), fix (2), uses (2), instructions (2), before (2), caused (2), javascript (2), features (2), been (2), explicitly (2), name (2), add (2), available (2), probably (2), please (2), machine (2), building (2), some (2), swap (2), space (2), out (2), called (2), reported (2), command (2), usage (2), there (2), fixes (2), find (2), installation (2), brew (2), update (2), ember (2), cli (2), workarounds (2), console (2), terminal (2), here (2), echo (2), 524288 (2), tee (2), etc (2), conf (2), similar (2), operating (2), see (2), watchers (2), path (2), moving (2), bug (2), folder (2), copyright, 2025, inc, social, contributor, covenant, twitter, discussions, stack, overflow, community, learn, get, alternatives, ejecting, previous, last, lewis, llobera, 2020, edit, seeing, old, version, either, avoiding, dependency, syntax, upgrading, migration, changelog, was, third, party, minifier, couldn, handle, during, has, solved, compiling, standard, higher, work, importing, multiple, way, later, switch, between, calling, example, specific, bundle, notice, english, default, large, subset, all, provided, may, case, sensitive, filenames, refer, section, completely, sure, didn, terminate, consider, locally, adding, failed, exited, means, ran, someone, kill, machines, limited, which, common, cloud, environments, even, small, projects, increase, ram, hundreds, megabytes, less, than, message, also, reports, nothing, else, helps, remove, again, uninstalling, still, launchctl, unload, library, launchagents, com, plist, documentation, other, methods, reinstall, shutdown, server, installing, newer, commands, homebrew, 6259, 358, jest, 1767, recommend, deleting, first, numerous, mentioned, issues, yarn, install, gets, stuck, after, printing, described, 713, then, paste, press, enter, could, information, max, user, watches, archlinux, instead, debian, redhat, another, distribution, increasing, setting, enospc, limit, number, reached, none, solutions, leave, comment, thread, runs, virtual, such, vagrant, provisioned, virtualbox, directory, exist, ensures, next, time, polling, mode, necessary, chokidar_usepolling, true, env, allow, tweak, settings, contains, parentheses, without, editors, like, vim, intellij, safe, write, feature, currently, breaks, disable, follow, adjusting, text, editor, referencing, restart, index, dropbox, check, entrypoint, typescript, show, errors, any, source, but, reloads, they, directly, indirectly, entrypoints, happen, when, save, while, browser, should, refresh, code, support, advanced, deployment, back, end, integration, testing, styles, assets, development, getting, welcome, search, deprecated, read, skip, main, content,

Text of the page (random words):
troubleshooting create react app skip to main content create react app is deprecated read more here create react app docs help github search k welcome getting started development styles and assets building your app testing back end integration deployment advanced usage support troubleshooting on this page troubleshooting npm start doesn t detect changes when you save a file while npm start is running the browser should refresh with the updated code if this doesn t happen try one of the following workarounds check that your file is imported by your entrypoint 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 if your project is in a dropbox folder try moving it out 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 some editors like vim and intellij have a safe write feature that currently breaks the watcher you will need to disable it follow the instructions in adjusting your text editor if your project path contains parentheses try moving the project to a path without them this is caused by a webpack watcher bug on linux and macos you might need to tweak system settings to allow more watchers 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 if none of these solutions help please leave a comment in this thread npm start fail due to watch error 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 you are running debian redhat or another similar linux distribution run the following in a terminal echo fs inotify max_user_watches 524288 sudo tee a etc sysctl conf sudo sysctl p copy if you are running archlinux run the following command instead echo fs inotify max_user_watches 524288 sudo tee etc sysctl d 40 max user watches conf sudo sysctl system copy then paste it in your terminal and press on enter to run it you could find more information here npm test hangs or crashes on macos sierra if you run npm test and the console gets stuck after printing react scripts test to the console there might be a problem with your watchman installation as described in facebook create react app 713 we recommend deleting node_modules in your project and running npm install or yarn if you use it first if it doesn t help you can try one of the numerous workarounds mentioned in these issues facebook jest 1767 facebook watchman 358 ember cli ember cli 6259 it is reported that installing watchman 4 7 0 or newer fixes the issue if you use homebrew you can run these commands to update it watchman shutdown server brew update brew reinstall watchman copy you can find other installation methods on the watchman documentation page if this still doesn t help try running launchctl unload f library launchagents com github facebook watchman plist there are also reports that uninstalling watchman fixes the issue so if nothing else helps remove it from your system and try again npm run build exits too early it is reported that npm run build can fail on machines with limited memory and no swap space which is common in cloud environments even with small projects this command can increase ram usage in your system by hundreds of megabytes so if you have less than 1 gb of available memory your build is likely to fail with the following message the build failed because the process exited too early this probably means the system ran out of memory or someone called kill 9 on the process if you are completely sure that you didn t terminate the process consider adding some swap space to the machine you re building on or build the project locally npm run build fails on heroku this may be a problem with case sensitive filenames please refer to this section moment js locales are missing if you use a moment js you might notice that only the english locale is available by default this is because the locale files are large and you probably only need a subset of all the locales provided by moment js to add a specific moment js locale to your bundle you need to import it explicitly for example import moment from moment import moment locale fr copy if you are importing multiple locales this way you can later switch between them by calling moment locale with the locale name import moment from moment import moment locale fr import moment locale es moment locale fr copy this will only work for locales that have been explicitly imported before npm run build fails to minify before react scripts 2 0 0 this problem was caused by third party node_modules using modern javascript features because the minifier couldn t handle them during the build this has been solved by compiling standard modern javascript features inside node_modules in react scripts 2 0 0 and higher if you re seeing this error you re likely using an old version of react scripts you can either fix it by avoiding a dependency that uses modern syntax or by upgrading to react scripts 2 0 0 and following the migration instructions in the changelog edit this page last updated on 2 13 2020 by lewis llobera previous alternatives to ejecting npm start doesn t detect changes npm start fail due to watch error npm test hangs or crashes on macos sierra npm run build exits too early npm run build fails on heroku moment js locales are missing npm run build fails to minify docs get started learn react community stack overflow github discussions twitter contributor covenant social github copyright 2025 facebook inc