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
{{ message }}
This repository was archived by the owner on Jun 3, 2019. It is now read-only.
* update eslintrc line-breaks for windows
* add prop-types as a dependency to prevent react-hot-loader from breaking build.
add cross-env for starting tasks which break on Windows.
add FAQ for when running develop and javascript files aren't loading even though the build is successful.
modify the clean task to execute a function rather than use the ${npm bin} exec command, which doesnst work on Windows.
* save exact package.json
* add cross-env to npm scripts
Copy file name to clipboardExpand all lines: internal/docs/FAQ.md
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -62,3 +62,9 @@ git merge upstream/master
62
62
# Deal with the merge conflicts, delete the yarn.lock file and
63
63
# rebuild it, then commit and push.
64
64
```
65
+
66
+
___Q:_____My development server starts and bundles correctly, but the JavaScript bundles don't load. What causes this to happen?__
67
+
68
+
Chances are you might be running on Windows. By default the server is bound to `0.0.0.0` for compatibility with Docker and other services. Everything is functioning correctly. The server listens fine on `0.0.0.0` and the problem is only client-side. Windows doesn't like to connecting to `0.0.0.0`. Change the host value in `config/values.js` to `localhost` or `127.0.0.1`. Another option is to specify `HOST=127.0.0.1` in the develop task within your `package.json` or `.env` file.
0 commit comments