error reading values after opacity

[nissoh]

@mixin opacity($opacity) {
  opacity: $opacity;
  // IE8 filter
  filter: alpha(opacity = ($opacity * 100));
}

also fails at this mixin

@mixin gradient-horizontal($startColor: #555, $endColor: #333) {
  filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#{ie-hex-str($startColor)}', endColorstr='#{ie-hex-str($endColor)}', GradientType=1); // IE9 and down
}

"error reading values after "gradient"

[LaurentGoderre]

To solve this you can use the unquote functionality:

@mixin opacity($opacity) {
  opacity: $opacity;
  // IE8 filter
  filter: unquote("alpha(opacity = (#{$opacity * 100}))");
}

[LaurentGoderre]

This is because libsass doesn't support that syntax.

[andrew]

Closing as it's a libsass problem rather than node-sass

[mattheworiordan]

FYI, I have the same issue.

[kennethormandy]

@mattheworiordan Just so you know, the issue in libsass is here if you want to keep tabs on it: sass/libsass#154

[mattheworiordan]

@kennethormandy, thanks.

[TomGault]

Looks like sass/libsass#154 is now fixed! Could update the libsass submodule and give it a try? I tried but I'm getting a million char type-mismatches errors from msbuild. I'm guessing it's not designed to be built in Windows. :S

[LaurentGoderre]

It is supposed to work. I am on Windows and am not getting any error

[TomGault]

Ah, interesting. Which compiler? I'm using VS2013. That is, on error I get: gyp ERR! stack Error: 'C:\Program Files (x86)\MSBuild\12.0\bin\msbuild.exe' failed with exit code: 1.

Should I create a different issue for the compilation problem? Even if it's just me being a n00b it might be good to keep a log of our troubleshooting.

[LaurentGoderre]

It's weird because @andrew and @nschonni worked on a solution where you don't need to build. It just uses precompiled binaries instead. I'm not exactly sure how it works though.

[TomGault]

I just ran "npm install" and got a bunch of C++ errors. Actually the errors seem to be from two different versions of compilers (VC9 and VC13). I have a lot of compilers on this box! :S

[LaurentGoderre]

Actually, you probably shouldn't compile it for Windows because it took me week to make it work.

[TomGault]

@LaurentGoderre and I took the discussion offline to investigate and found there was a misunderstanding. You can "build" node-sass using npm like normal on Windows if you want to just include it in another project, however actually setting up a development environment on Windows is tricky.