-
-
Notifications
You must be signed in to change notification settings - Fork 3.3k
Update docs with troubleshooting information: watching section #1779
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update docs with troubleshooting information: watching section #1779
Conversation
src/content/configuration/watch.md
Outdated
|
||
## Webpack doesn't recompile on change while watching | ||
|
||
### File changes are being seen, just no files are being updated |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
File changes are seen, but no files are updated
src/content/configuration/watch.md
Outdated
|
||
### File changes are being seen, just no files are being updated | ||
|
||
Verify that webpack is not being notified of changes by running with the --progress flag. If progress shows on save but no files are output, it is likely a configuration issue, not a file watching issue. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would suggest a small grammar and formatting tweak…
running webpack with the --progress
flag
src/content/configuration/watch.md
Outdated
|
||
### File changes are being seen, just no files are being updated | ||
|
||
Verify that webpack is not being notified of changes by running with the --progress flag. If progress shows on save but no files are output, it is likely a configuration issue, not a file watching issue. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
no files are outputted
src/content/configuration/watch.md
Outdated
cat /proc/sys/fs/inotify/max_user_watches | ||
``` | ||
|
||
Arch users, add `fs.inotify.max_user_watches=524288` to `/etc/sysctl.d/99-sysctl.conf` and then execute `sysctl --system`. Ubuntu users (and possibly others): `echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
src/content/configuration/watch.md
Outdated
### macOS fsevents bug | ||
|
||
On macOS folders can get corrupted. See this article: | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@EugeneHlushko You can probably just combine the 'See this article' text with the link for the article.
src/content/configuration/watch.md
Outdated
|
||
### Windows paths | ||
|
||
webpack expects absolute paths for many config options. `__dirname + "/app/folder"` is wrong, because windows uses `\` as path separator. This breaks some stuff. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@EugeneHlushko How about…
Because webpack expects absolute paths for many config options such as
__dirname + "/app/folder"
the Windows\
path separator can break some functionality.
src/content/configuration/watch.md
Outdated
|
||
### Vim | ||
|
||
On some machines Vim is preconfigured with the [backupcopy option](http://vimdoc.sourceforge.net/htmldoc/options.html#'backupcopy') set to **auto**. This could potentially cause problems with the system's file watching mechanism. Switching this option to `yes` will make sure a copy of the file is made and the original one overwritten on save. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@EugeneHlushko Personally I think auto should be auto
as it's config.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for your submission @EugeneHlushko I have a few small suggestions…
Thanks @ChrisChinchilla all seems legit, i will update PR today |
6234a2f
to
b7fc618
Compare
@ChrisChinchilla its updated now, pls take a look |
@EugeneHlushko Looks good, thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this addition @EugeneHlushko. I think the content is great and the grammar seems fine, my only issue is the header structure. See my comments for more info and let me know if I can clarify anything.
src/content/configuration/watch.md
Outdated
@@ -70,3 +70,44 @@ poll: 1000 // Check for changes every second | |||
|
|||
T> If watching does not work for you, try out this option. Watching does not work with NFS and machines in VirtualBox. | |||
|
|||
# Troubleshooting |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We shouldn't have two h1
s on the page. Can you switch this to a ##
and add an extra line break before it (we typically use two before ##
headers).
src/content/configuration/watch.md
Outdated
@@ -70,3 +70,44 @@ poll: 1000 // Check for changes every second | |||
|
|||
T> If watching does not work for you, try out this option. Watching does not work with NFS and machines in VirtualBox. | |||
|
|||
# Troubleshooting | |||
|
|||
## Webpack doesn't recompile on change while watching |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would rather see more concise titles here as very long ones won't be very intuitive or easy to display in our side nav, e.g.:
For example, maybe the following would work better and still convey the idea:
### Missed Compilations
Please consider the same change for the rest of the longer headers. Also note that I changed this to an h3
to properly nest it under:
## Troubleshooting
Another option would be to simply change them from headers to bold text, for example:
Troubleshooting
If you are experiencing any issues, please see the following notes. There are a variety of reasons why
webpack might miss a file change.Changes are seen, but no files are updated
...
Not enough watchers
...
432dfbc
to
701a8a4
Compare
Hi @skipjack |
Hi @skipjack |
See the end of my comment from before (quoted below), personally I think you should update it like so (and drop
This approach means you don't have to shorten each subsection title but we won't have the run-on title issue in the sidebar. |
Thank you for clarification @skipjack ! 👍 |
After accidentally getting onto @sokra and @gaearon discussion of old docs missing page on twitter, i decided to send a PR with troubleshooting section for webpack watch. This makes it easier to find and to make people link to our docs website instead of old wiki page.