Open onlyskyguy opened 8 years ago
Hmmm, your settings seem right.
I think this might be a problem with the fact that gulp-sass
is a wrapper around node-sass
, which is a node binding for libsass
, which is a port of Sass
. So it's very likely that one of those projects it's getting confused with the PATH.
Does the command work in the terminal?
Yes it works great in terminal.
Yeah there's a lot sass going on :p On Sep 18, 2015 6:07 AM, "Nicolás Santángelo" notifications@github.com wrote:
Hmmm, your settings seem right.
I think this might be a problem with the fact that gulp-sass is a wrapper around node-sass, which is a node binding for libsass, which is a port of Sass. So it's very likely that one of those projects it's getting confused with the PATH.
Does the command work in the terminal?
— Reply to this email directly or view it on GitHub https://github.com/NicoSantangelo/sublime-gulp/issues/50#issuecomment-141446438 .
Welp, I'm having the same error and it's not an easy fix :( I'll let you know if I find something
Does it have to do with local node files vs global? Or due to all the wrapper action involved with libsass On Sep 20, 2015 9:05 AM, "Nicolás Santángelo" notifications@github.com wrote:
Welp, I'm having the same error and it's not an easy fix :( I'll let you know if I find something
— Reply to this email directly or view it on GitHub https://github.com/NicoSantangelo/sublime-gulp/issues/50#issuecomment-141803683 .
The solution to this might be somewhere in the gulp-sass arena, but I'm only getting the following error when I run gulp with sublime-gulp. If I run normally from a terminal it works fine.
I'm wondering if I've got something setup incorrectly in the sublime-gulp settings for this to happen.
Running Ubuntu Linux
gulp.sublime-settings
Thanks for any insight into this.