-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Create a troubleshooting guide #916
Comments
Maybe we could write it on a wiki here? |
I reaaalllyy dislike wikis for just about anything. I'd rather a TROUBLESHOOTING.md. Documents in repos are better for a bunch of reasons
@sindresorhus has written on the topic and I completely agree - https://plus.google.com/+sindresorhus/posts/QSS2du26Mg4 |
On Sat, 2 May 2015, Michael Mifsud wrote:
Ah, didn't know that
True for wikis as well
I fully agree that the guide should be in the TROUBLESHOOTING.md The point is just to get started and collect issues - unfortunately Wiki stuff copy-edited should go into the repo, no question. |
True but it requires as separate checkout and most people aren't away wikis are also repos. You still can't PR them though, so it's hard to get community involvement.
Completely agree. This issue a place holder, and a single point of reference for when the document is being written. I didn't want to have to crawl through the issue tracker. |
We need a trouble shooting guide addresses some common issues. This will hopefully cut down on duplicate issues.
Useful resources
node-sass installation debug script (Windows)
https://gist.github.com/am11/e5de3c49c219f0811e1d
node-sass installation debug script (Linux/Mac)
https://gist.github.com/am11/9f429c211822a9b15aee
Common issues
Assertion failed: (handle->flags & UV_CLOSING), function uv__finish_close, file ../deps/uv/src/unix/core.c, line 209
with node-sass < 3.0.0The text was updated successfully, but these errors were encountered: