Michael Mifsud

As a work around I've released 3.5.4 which the sass2scss bump reverted since we need to get the node-sass release out.

Considering this is causing compilation failures, it's clear this isn't a simple noop like a JS linter would be. I have very mixed feelings, I'm all for some kind of...

I'd rather incrementally formatting files as we touch them rather than a big bang commit. My suggestion would be to commit the configuration, and for us to configure our editors...

Off topic. @am11 you might be interested in this if you haven't seen it https://github.com/medialize/sass.js/ On 9 Feb. 2017 6:32 am, "Adeel Mujahid" wrote: > This is great! I actually...

This should probably be out on hold as the upcoming module system won't be compatible. On Thu., 28 Feb. 2019, 7:55 am Bit Connor, wrote: > ping @glebm > >...

@chriseppstein simplefilewatcher looks promising from a glance. As an alternative for the moment I've just supercharged the watcher in node-sass. It's now aware of the `@import` dependency graph and will...

Noone is currently working on this. Our priority right now is getting Ruby Sass parity. If you're using node/io.js [node-sass](https://github.com/sass/node-sass) currently has a great watcher. There are also binding for...

There no plans to implement this in the near future. Pull requests are welcome.

My thoughts from gitter conversation ``` - I'm all for dumping ruby where ever possible - But sass-spec also does a little more than just run tests - It has...

I have a fix for the error reported (#2846) but not the underlying issue of executing scoped function references. Until the behavioural issue is resolved erring is better than producing...