eliminate ruby dependency about sass-brunch

[paulmillr]

we have compass-brunch -- it can support compass and our version would support pure sass

[es128]

The more I think about it, the more I'm liking the idea of giving this plugin the smarts to use node-sass when viable, fallback to the gem automatically, and print informative error messages when compass is being used without the gems being available. The only drawback is installation of node-sass as a dependency when it isn't necessary for compass users, but that's not such a big deal - plus they can use compass-brunch instead if it bothers them.

Any objections to that?

Although I'd still like to hear from brunch + sass - compass users about this. As nice as I think that setup would be, I'm not sure yet if it's worth the effort, or whether it would actually help anybody.

[paulmillr]

it's cool, but let's hear someone else's opinions

[DjebbZ]

Haven't used brunch for a while, and not a Compass user, so the possibility to not rely on Ruby in the whole stack just sass looks appealing. This would speed up the build/watch process. Docpad already has both versions of its sass plugin. My 2 cents (really worth 2 cents though).

[soundyogi]

+1
I'd love to be able to use the scss version of foundation without all that ruby-hassle :C ! Do not care about Compass though ^^

[es128]

Well, that's one!

Although your auto-avatar looking suspiciously like a middle finger makes me a bit nervous. 😲

[lionelB]

:+1 for remove ruby dependency and uses bourbon!

[vendethiel]

+1 too :).

[lionelB]

I think both plugins are valuable.

• One providing support to Compass and based on the ruby version of Sass
• One providing a Sass-only based on the nodejs binding of libsass

[es128]

@lionelB I plan to support both within this plugin

[lionelB]

Since compass is only compatible with Sass ruby, support both versions of Sass transparently is a great news :)

[Elexy]

+1, don't care for compass, and like to be able to get rid of ruby dependency. Giving me headache deploying on OpenShift.

[john-kurkowski]

+1

[es128]

No more +1s needed to convince me this is worth doing. I intend to work on it soon.

[nybblr]

Big +1 here =) I'm using brunch on a Raspberry Pi, and while the node installation is pretty quick, downloading/compiling a Ruby is brutal (over 2 hours).

[jsdir]

+1

[paulmillr]

Check 1.7.3 later today folks.

[nybblr]

Sweet! Thanks @paulmillr

[jsdir]

Thanks @paulmillr. Goodbye ruby!

[virtualfunction]

Can I ask what the sassRe is doing here. It seems that .sass files are compiling with ruby. I'm using bourbon with .sass files but have no need for Ruby. I'm hacking round it with a cheeky SassCompiler::_rubyCompile = SassCompiler::_nativeCompile line in my brunch-config.coffee file

[pikeas]

Same problem here, why does sass-brunch send .sass files to Ruby's sass gem instead of to node-sass?

@virtualfunction's hack worked for me with a slight modification:

SassCompiler = require('sass-brunch')
SassCompiler.prototype._rubyCompile = SassCompiler.prototype._nativeCompile