You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add note for using CHOKIDAR_USEPOLLING in virtual machines to enable HMR (facebook#1608)
* Add note for using CHOKIDAR_USEPOLLING in virtual machines to enable HMR
* Use br in react-scripts template README md
* Use br in md for new line breaks
* Update troubleshooting HMR to allow for VMs running Windows
* Fix up the instructions
@@ -402,7 +402,7 @@ Then in `package.json`, add the following lines to `scripts`:
402
402
"test": "react-scripts test --env=jsdom",
403
403
```
404
404
405
-
>Note: To use a different preprocessor, replace `build-css` and `watch-css` commands according to your preprocessor’s documentation.
405
+
>Note: To use a different preprocessor, replace `build-css` and `watch-css` commands according to your preprocessor’s documentation.
406
406
407
407
Now you can rename `src/App.css` to `src/App.scss` and run `npm run watch-css`. The watcher will find every Sass file in `src` subdirectories, and create a corresponding CSS file next to it, in our case overwriting `src/App.css`. Since `src/App.js` still imports `src/App.css`, the styles become a part of your application. You can now edit `src/App.scss`, and `src/App.css` will be regenerated.
408
408
@@ -1355,10 +1355,10 @@ You can find instructions in [Deploying React with Zero Configuration](https://b
1355
1355
1356
1356
Sometimes `npm run build` works locally but fails during deploy via Heroku with an error like this:
1357
1357
1358
-
```
1358
+
```
1359
1359
remote: Failed to create a production build. Reason:
1360
1360
remote: Module not found: Error: Cannot resolve 'file' or 'directory'
1361
-
MyDirectory in /tmp/build_1234/src
1361
+
MyDirectory in /tmp/build_1234/src
1362
1362
```
1363
1363
1364
1364
This means you need to ensure that the lettercase of the file or directory you `import` matches the one you see on your filesystem or on GitHub.
@@ -1452,6 +1452,7 @@ If this doesn’t happen, try one of the following workarounds:
1452
1452
* 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 [“Working with editors supporting safe write”](https://webpack.github.io/docs/webpack-dev-server.html#working-with-editors-ides-supporting-safe-write).
1453
1453
* If your project path contains parentheses, try moving the project to a path without them. This is caused by a [Webpack watcher bug](https://github.com/webpack/watchpack/issues/42).
1454
1454
* On Linux and macOS, you might need to [tweak system settings](https://webpack.github.io/docs/troubleshooting.html#not-enough-watchers) to allow more watchers.
1455
+
* If the project runs inside a virtual machine such as (a Vagrant provisioned) VirtualBox, run `npm install --save-dev cross-env`in its root folder and then replace `"react-scripts start"`in the `scripts` section of its `package.json` with `"cross-env CHOKIDAR_USEPOLLING=true react-scripts start"`. This ensures that the next time you run `npm start`, the watcher uses the polling mode, as necessary inside a VM.
1455
1456
1456
1457
If none of these solutions help please leave a comment [in this thread](https://github.com/facebookincubator/create-react-app/issues/659).
0 commit comments