-
Notifications
You must be signed in to change notification settings - Fork 381
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
Assertion `val->IsString()' failed #57
Comments
When doing what? |
gulp.src('app/styles/themes/' + method.name + '.scss')
.pipe($.sass({
errLogToConsole: true,
includePaths: ['app/bower_components'],
sourceComments: 'map'
})) On second thoughts, I think this is a node-sass bug. |
Yeah, that's either libsassc or node-sass. |
I have the same issue upgrading past 0.7.1, FWIW, so I'm currently locked at that version. |
👍 Having the same issue. Downgrading to 0.7.1 fixes it. |
So something's changed/broken in node-sass here. I'm not sure there's anything I can do about it short of rolling back the dependency, but I'll get into it this weekend. Downgrade to 0.7.1 as suggested if you can't get around the problem |
The issue discussion at node-sass: sass/node-sass#337 |
+1 |
1 similar comment
+1 |
when i convert a empty sass file to css, i get this error and downgrading to 0.7.1 fixes it. |
👍 |
1 similar comment
+1 |
It's the source maps option |
Unfortunately 0.7.1 doesn't like a / some Bourbon / Neat mixin(s) so ... we'll have to make do without source maps for the time-being and resume 0.7.2 |
Any luck with Bourbon and Neat? { |
still broken for me when updating to 0.7.2 with node-sass 0.9.3, works on 0.7.1 with node-sass 0.8.6 |
Should be fixed with 57b7a6c |
With your latest release I'm getting |
This is a node-sass bug. See sass/node-sass#378 |
We get this error since we upgraded from version 0.7.1 to 0.7.2:
The text was updated successfully, but these errors were encountered: