-
Notifications
You must be signed in to change notification settings - Fork 465
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
Throws when data && file are null (an edge case) #776
Comments
This should be fixed and you should now get a proper error on the context! |
Thanks @mgreter! 👍 I will try it now. |
@mgreter, somehow the errors which were previously returned as JSON are coming as plain text. Is there something changed in |
Nope, this should behave the same as before! |
After pulling the latest libsass master, it is giving me a plain text error: require("node-sass").renderSync({data:"messing around"})
source string:1: error: invalid top-level expression Which was previously producing: {
"status": 1,
"file": "stdin",
"line": 1,
"column": 1,
"message": "invalid top-level expression"
} And segmentation fault if data is an empty string: require("node-sass").renderSync({data:""})
Segmentation fault |
Sorry for the cry-wolf, recompiling fixes it! (crazy things happening today here) :) |
When an empty option set is sent to libsass, it chokes. :)
Same thing happens, when
file
anddata
options are empty or null.Originally reported by @DinisCruz: sass/node-sass#554.
The text was updated successfully, but these errors were encountered: