Expected 'in' keyword in @each directive

[visualcookie]

Hi,

I manually "installed" Susy in a project. As soon as I call the susy.scss file I get an error in console.

Any ideas? Didn't changed anything just Drag & Dropped it into my projects folder.

INFO: I'm using LibSass. Could this be the problem?

Dean Hidri

[mirisuzanne]

What version of libsass are you using? That was the error that you would get before Libsass added support for looping over maps.

[mirisuzanne]

Looks like node-sass (and gulp-sass by association) are still using an older version of libsass. Hopefully we can get them to release updates asap.

[visualcookie]

Ye, I'm using node-sass together with Grunt. Hope that too, because I really wanna work with Susy.

[gionkunz]

node-sass is at https://github.com/sass/libsass/tree/5f3558d7ce36bb61202f1585ed8e32a52209e940 and sass/libsass@f55b2d5 was actually a few days earlier. I believe grunt-sass is outdated. They are still at node-sass 1.0.3 rather than 1.2.3. I wanted to check grunt-sass and do a PR but things are worse. Lib sass used by node-sass 1.2.3 is actually failing to install (on my machine at least) because something with their binary check is wrong in the lib-sass version node-sass 1.2.3 is using. When failing back to node-sass 1.2.2 I can now see that varargs are not supported as I get susy/output/shared/inspect:19: invalid top-level expression

I love Sass and I really appreciate lib-sass as I don't use Ruby and appreciate the speed the C wrapper gives. However, this story is the same all over and over.

I guess the only solution to this problem would be to start a Sass specification WG :-) I'd even pay for this!

[visualcookie]

@gionkunz Good grief. Why it's so complicated? Just started to get LibSass running well and then it won't work with grunt-sass due old version. On Issues Board there are tons of requests that grunt-sass should be updated, but it doesn't seem to happen. 😢

Is there another Grunt package out there that powers LibSass and works well? Would appreciate it!

EDIT: Manually installed node-sass 1.2.3 in the grunt-sass folder. Worked, but it keeps throwing up errors. I think I'll make a cut here and wait til it all gets updated. Really wanted to check out Susy.

[wtran]

+1 I'm having the same issue with the manual install

[mirisuzanne]

Actually, that invalid top-level expression error is a good sign. It means you're on the wrong version of Susy. That was a syntax error that ruby didn't care about, but libsass does. Make sure you are using Susy 2.2.0.beta.2 for testing against any version of libsass.

Maybe node-sass 1.2.2 will work then?

[zellwk]

I have the same problem too, and I'm using Grunt Sass. Will probably cut back and wait a little longer :)

[visualcookie]

@ericam Will try it out tomorrow. Thanks for the tip. 👍

[mirisuzanne]

Looks like npm install gulp-sass@beta may be working for people over on #406

[visualcookie]

@ericam Installed Susy 2.2.0.beta.2 via gem install susy --pre and added require 'susy' to the Gruntfile, but the console outputs now that the file to import was not found or is unreadable: "susy".

Did I do something wrong? And what would be the solution?

EDIT Oh, still did @import "susy"; in my Sassfile. Did removed that but now he can't seem to find the Susy-Gem. :(

EDIT OF THE EDIT Okay, used the branches tree and navigated to the working LibSass version. Now it works. No problems.

[mirisuzanne]

Glad to hear it worked (with a few edits)! :)

[josephspens]

As of today (12/20) running the latest grunt-sass I installed susy 2.2.0.beta.2 and all works now.

These days using LibSass is like playing Russian Roulette with Sass package versions.

[visualcookie]

Well I moved back to Ruby Sass and Grunt. I need some SassScript stuff at the moment, and LibSass doesn't support it at the moment.

[KittyGiraudel]

I believe this comes from the fact that you were using an outdated version of Sass which did not support this version of the @each loop.