-
Notifications
You must be signed in to change notification settings - Fork 103
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
libsass compatibility? #6
Comments
I'm also facing this issue |
You guys should be using https://github.com/sindresorhus/gulp-ruby-sass. Anyway @akhleung, @appleboy, @am11 or @hcatlin let us know when it becomes compatible with libsass. |
As far as I can tell, the language spec parity is getting closer in libsass. Which version of node-sass are you testing with? Just today we upgraded grunt-sass to use latest node-sass beta (v3): See sindresorhus/grunt-sass#196 (comment). You can give it a try or against the vanilla node-sass API: Nonetheless, if you find a missing language feature, please consider opening issue in libsass issue tracker: https://github.com/sass/libsass. |
Just tested it using the latest version of gulp-sass. It's working on gulp-sass 2.1.0 which is using node-sass 3.4.1 which is using libsass 3.3.1. So it works on libsass 3.3.1. |
Hey,
I just tried to use the project with gulp-sass (which is using node-sass depending on libsass) but it fails on some things like arrays.
Do you think it would be possible to test it against libsass and ensure compatibility?
Thanks,
Anselm
The text was updated successfully, but these errors were encountered: