compass dependencies not captured about ember-blog HOT 6 CLOSED

The package uses sass-brunch to add compass support, which runs node-sass to run libsass, a faster C++ port of the Ruby-based SASS compiler. It's not immediately clear which version of SASS libsass is up-to-date with but the repo says it's not quite got full parity with v3.2.

I definitely agree that adding a gemfile seems odd. This PR was supposed to remove the Ruby dependency for SASS/compass from brunch-sass. However, I'm not 100% sure how it's loading Compass now, or how to run it without the gem. This might be a possibility. Basically, we need to find a libsass-compatible version of compass that isn't a gem.

I have SASS and Compass installed on my machine as gems: Compass is v0.12.2 and SASS is 3.2.10

from ember-blog.

I am trying to run ember-blog and am running into the same problem with brunch watch -s. I tried npm installing sass-brunch and node-sass and am still getting the same error.

from ember-blog.

@adamrneary @sir-dunxalot I figured out the problem on my computer. I did a sudo gem uninstall sass to get rid of all versions of sass (I had 5) and sudo gem uninstall compass. Then I did sudo gem install compass which got the version of sass that compass needed. I read somewhere else that compass could have been having problems because it was getting run with an incompatible version of sass.

from ember-blog.

Thanks for following up on this. Since I have tons of other projects using
a particular version of Sass, that would probably be a blocker for me.
Thinking more generally, since compass is ruby-based, it might not be a
perfect fit for a javascript-oriented static site platform. Perhaps
something to store away for the roadmap. For now, I managed to get assemble
working, so I've been using that. :/

On Wed, Jul 9, 2014 at 11:11 AM, Bart Szyszka [email protected]
wrote:

@adamrneary https://github.com/adamrneary @sir-dunxalot
https://github.com/sir-dunxalot I figured out the problem on my
computer. I did a sudo gem uninstall sass to get rid of all versions of
sass (I had 5) and sudo gem uninstall compass. Then I did sudo gem
install compass which got the version of sass that compass needed. I read
somewhere else that compass could have been having problems because it was
getting run with an incompatible version of sass.

—
Reply to this email directly or view it on GitHub
#5 (comment)
.

[email protected] [email protected]
www.adamrneary.com
@adamrneary https://twitter.com/adamrneary
+1 617-830-1854

from ember-blog.

Sorry for the delayed response.

So long as you have the Compass gem installed globally, I believe lib-sass will use that installation. However, to be honest, I do not fully understand gems and gem settings. The issues above may be to do with gem sets being installed into the bundle directory depending on your rbenv settings (maybe?). I have used the Brunch/lib-sass pairing on many builds before so I'll see if one of the guys I worked with on those projects can take a look at this and see what is going on. I guess it's hard to replicate the 'fresh build' environment without a VM/vagrant. I do apologize for my oversight here.

The reason I haven't been contributing recently is because (besides personal stuff) I've been debating transitioning this skeleton to ember-cli before ember-blog gets too big and official. That would mean defaulting to the ruby port of SASS until this issue is resolved. I know that's outside the scope of this conversation but it's a potential solution. Downside is massively slower dev time because of slow ruby sass compilation time.

from ember-blog.

Closed with rebuild - addon now has a complete rewrite and focusses on adding to an existing Ember app only (not doing any styling).

from ember-blog.