Marcin Cieślak

There is a proposal in #1156 to split CLI as the separate module and I think this is a good way to fix our hopelessly broken command line interface (in...

lib/watcher.js is already a progress, but the way it is called from node-sass binary needs to be refactored

How should it work?

Would that be possible to create a simple demo repository to demonstrate the case - and most importantly to show what the expected output would be?

Thanks @jvretamero - in your case you need to figure out which part of your project keeps node-sass version low (for example by requiring `^4.9`). Sometimes one has to find...

It is possible if some one steps up with patches to our Travis CI build environment or builds its own and uploads binaries for every release.

If you look at the [node-sass releases page](http://github.com/sass/node-sass/releases) we are publishing binary modules for almost every node binary API version out there (since 0.10). But for example `musl` binaries are...

There is nothing that prevents node-sass from running on Android - if someone contributes a stable binary-building process ARM binaries can be made easily available.

The second issue (`body{background:blue}\nbody{background:blue}`) is already covered in https://github.com/sass/node-sass/issues/1152, so let's focus here on change notifications caused by #2268

It looks to me that https://github.com/sass/node-sass/issues/2491 https://github.com/sass/node-sass/issues/2504 https://github.com/sass/node-sass/issues/2560 and partially https://github.com/sass/node-sass/issues/2479 have the similar root cause. We constantly maintain a graph of dependencies and we try to rebuild everything on...