-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Update libsass to fix #132 and #189 #190
Comments
👍 |
This should be fixed as libsass has been recently updated to today's master branch. Of course, it may take a few days for @andrew to publish a new set of binaries, but I will close out this issue for now. |
Any chance that this will be updated soon? |
Mainly waiting on a windows binary, hopefully I'll be able to get a release out this weekend. |
That would be amazing. Thanks! |
No pressure huh! ;) The only holdup is the 32 bit version which won't compile for some reason. |
There you go! sass/node-sass-binaries#2 |
How do windows binaries get built? Is there such thing as a windows build machine? |
For the meantime I build them.... |
I wish there was a windows build machine! |
Shipped v0.8.0: https://github.com/andrew/node-sass/releases/tag/v0.8.0 |
You, sir, are a prince! |
@ericjorgensen it's thanks to lots of help from @nschonni, @LaurentGoderre and @deanmao |
fix typos in README.md
#132 and duplicate issue #189 were closed because the problem was with libsass, not node-sass. Well, libsass now claims that sass/libsass#154 is now fixed so we should update our submodule to get the fix.
The text was updated successfully, but these errors were encountered: