gulp-ruby-sass can't find @import'd files #63
Comments
I haven't read the latest source but believe that gulp-ruby-sass copies the |
Your source glob has to include all of your Sass files. Is there a reason Rob Wierzbowski On Fri, Jun 27, 2014 at 1:22 AM, Fabrício Matté notifications@github.com
|
@robwierzbowski oh no reason really, it's just that that way works with Thanks, this fixes the compilation issues. Might be worth adding a note about this somewhere if there isn't one yet. |
Test case file structure:
scss/app.scss
scss/_mixins.scss
Throws:
Now if I add the absolute path to the
scss
directory in theloadPath
option, it compiles but the sourcemap throws an warning as in #47 (can't determine the source files' public URL).I believe I shouldn't have to add an absolute path to
loadPath
in order to@import
using paths relative to the current scss file, this appears to be a regression bug.When not providing a
loadPath
, the directoryC:/Users/Ult/AppData/Local/Temp/gulp-ruby-sass
contains a copy ofapp.scss
and a directory_14139e58-9ebe-4c0f-beca-73a65bb01ce9
containing the outputcss
file whose content is:Running node 0.10.26, gulp 3.8.3, latest gulp-ruby-sass (
git://github.com/sindresorhus/gulp-ruby-sass.git#83bce4ce1317185add687934c3ec77db3cf0cba6
), Windows 7 x64 Ultimate.The text was updated successfully, but these errors were encountered: