search

francocatena / meteor-compass

MIT License
14 stars 2 forks source link

When will the new #1

Open saberone opened 9 years ago

saberone commented 9 years ago

I'm trying to get susy to work in meteor using meta:susy. Both fourseven:scss and francocatena:compass are added as packages to my meteor project.

This doesn't seem to work right now. I get the following message

.meteor/local/build/programs/server/assets/packages/meta_susy/susy/language/susy/settings:58: expected 'in' keyword in @each directive

The only thing that's in my .scss file is

@import "susy";

I saw that supposedly this is fixed in the experimental branch. But I'm very new to meteor and I don't know how to use the code in the experimental branch, instead of the package installed through : "meteor add

copleykj commented 9 years ago

I have this same exact issue, is there any way we could get this fixed?

francocatena commented 9 years ago

Hi Guys, sorry for the delay. The error seems related to libsass limited features support beyond SASS 3.1. I will explain this a little bit more and how can you fix (hopefully) the problem.

It all starts with node-sass, they use libsass which is yet "incomplete". You can read about it in: https://www.npmjs.com/package/node-sass#reporting-sass-compilation-and-syntax-issues

Then, the fourseven:scss package wraps node-sass, so no luck for features depending on SASS >= 3.2.

For this reason this package only supports Compass 0.13.alpha.4. Is the latest version I can get without "syntax errors" like the one described by @saberone.

¿What can we do?

1- Ask the meta:susy mantainer to downgrade to the latest "usable" version of the library with libsass 2- Make a Nodejs (or Meteor) wrapper for the official SASS compiler (currently depending on Ruby)

Regarding the alternative 2, I think is very unlikely we can get a self contained package with Ruby included... If it is not made this way a lot of people will be forced to install Ruby on their own, and also to consider this in the production environment (and in some cases, it will make impossible to deploy to meteor.com).

I hope this clarifies a bit... I will leave this issue open for a while so we can chat about workarounds.

Cheers.