Node-sass: render error callback not called on import path error

[maxlath]

following the removal of working directory-relative import (which I guess is the breaking change mentioned in #1474 ), compiling my old scss code rejected an error of the kind:

{
  "formatted": "Error: File to import not found or unreadable: ../bower_components/foundation/scss/foundation/components/alert-boxes\n       Parent style sheet: /home/maxlath/inventaire/client/app/modules/general/scss/foundation/_imports.scss\n        on line 29 of app/modules/general/scss/foundation/_imports.scss\n>> @import \"../bower_components/foundation/scss/foundation/components/alert-boxes\n   ^\n",
  "message": "File to import not found or unreadable: ../bower_components/foundation/scss/foundation/components/alert-boxes\nParent style sheet: /home/maxlath/inventaire/client/app/modules/general/scss/foundation/_imports.scss",
  "column": 1,
  "line": 29,
  "file": "/home/maxlath/inventaire/client/app/modules/general/scss/foundation/_imports.scss",
  "status": 1
}

But while I do get this error from the executable node-sass/bin/node-sass, I never get it from the module itself: binding.render is called, but neither the error nor the success, letting the callback passed to render hanging. Any clue where this difference of behavior comes from?

[maxlath]

I made a demo project of the error to illustrated a related issue in another project but that could be illustrative here too: you can see how sass-brunch is unable to pass an error to brunch due to node-sass not calling its error callback internally, while running node-sass executable triggers the error

[xzyfer]

following the removal of working directory-relative import

That is the Sass changelog, not Node Sass.

which I guess is the breaking change mentioned in #1474

It is not. Please take a moment to read the post before spreading misinformation like this:

A breaking change in node-sass made my build break, but apparently without properly rejecting the error.

---

A simple reduce test case shows the error is produced as expected

// index.scss
@import "no-such-file";

./node_modules/.bin/node-sass index.scss

{
  "formatted": "Error: File to import not found or unreadable: no-such-file\n       Parent style sheet: /Users/michael/tmp/issue-1592/index.scss\n        on line 1 of index.scss\n>> @import \"no-such-file\"\n   ^\n",
  "message": "File to import not found or unreadable: no-such-file\nParent style sheet: /Users/michael/tmp/issue-1592/index.scss",
  "column": 1,
  "line": 1,
  "file": "/Users/michael/tmp/issue-1592/index.scss",
  "status": 1
}

---

This appears to be an issue with brunch or which ever package is calling node-sass.

[maxlath]

@xzyfer my apologies for the mismatch on the breaking changes, I got to say I'm still confused on when the change on working directory import path happened then.

There is still something bothering me here:

• this test logs the expected error:

var sass = require('node-sass')
var options = {
  file: 'whatever'
}
sass.render(options, function(err, result){
  console.log('err', err)
  console.log('result', result)
})

• but this one stays silent and keeps eating the CPU

var sass = require('node-sass')
var options = {
  file: 'whatever',
  data: '@import \'../some/inexisting/file\';',
  includePaths: [ '.', 'app' ]
}
sass.render(options, function(err, result){
  console.log('err', err)
  console.log('result', result)
})

It seems it either has to do with the ../ path of the @import or the . in includePaths: if you remove either of those, you get your error message back. Is that still me doing something wrong here?

[xzyfer]

Thanks for your understanding. Using both data and file is unsupported and
results in defined behaviour. This is likely causing the issue you're
describing.
On 14 Jun 2016 7:22 PM, "maxlath" [email protected] wrote:

@xzyfer https://github.com/xzyfer my apologies for the mismatch on the
breaking changes, I got to say I'm still confused on when the change on
working directory import path happened then.

There is still something bothering me here:

• this test logs the expected error:

var sass = require('node-sass')var options = {
file: 'whatever'
}sass.render(options, function(err, result){
console.log('err', err)
console.log('result', result)
})

• but this case stays silent and keeps eating the CPU

var sass = require('node-sass')var options = {
file: 'whatever',
data: '@import \'../some/inexisting/file\';',
includePaths: [ '.', 'app' ]
}sass.render(options, function(err, result){
console.log('err', err)
console.log('result', result)
})

It seems it either has to do with the ../ path of the @import or the . in
includePaths: if you remove either of those, you get your error message
back.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/sass/node-sass/issues/1592#issuecomment-225826439,
or mute the thread
https://github.com/notifications/unsubscribe/AAjZWKRToHnfBtvI4-gAUyXwNbQeMIRDks5qLnLPgaJpZM4I0H8y
.

[maxlath]

Sorry to insiste, but it doesn't look like the issue is that I'm passing both file and data. We can actually remove file and still get a case without any error being returned:

• this gets the right error

var options = {
  data: '@import \'../some/inexisting/file\';',
  includePaths: [ 'app' ]
}

• this too

var options = {
  data: '@import \'./some/inexisting/file\';',
  includePaths: [ '.', 'app' ]
}

• but not this

var options = {
  data: '@import \'../some/inexisting/file\';',
  includePaths: [ '.', 'app' ]
}

[xzyfer]

Sorry to insiste, but it doesn't look like the issue is that I'm passing both file and data.

Sorry, to be clear, passing both data and file is probably why you're seeing the a different issue

this one stays silent and keeps eating the CPU

[xzyfer]

I am able to reproduce a process hang with

var sass = require('node-sass')
var options = {
  data: '@import "../does-not-exist";',
  includePaths: ['.']
}
sass.render(options, function(err, result){
  console.log('err', err)
  console.log('result', result)
})

[xzyfer]

After some digging it looks like the issue is with . being used a load path. Using __dirname or an absolute path instead works as expected.

[xzyfer]

I have confirmed this a bug in LibSass - https://github.com/sass/libsass/issues/2106

[michaelhogg]

The bug in LibSass was fixed in sass/libsass#2107, and the fix was released in v3.4.0.

The version of LibSass used by node-sass was bumped to 3.4.0 for release v4.0.0.

So I think this issue should be resolved in v4.0.0 onwards.