search

darrenkopp / SassyStudio

Visual Studio extension that adds a little bit of support for sass/scss
MIT License
101 stars 12 forks source link

No longer compiling files outside parent folder #45

Open funzeye opened 10 years ago

funzeye commented 10 years ago

Hi, It no longer seems to be able to compile my Bourbon files, which are one level back out from the parent scss file.

sample error message: ...error: file to import not found or unreadable: "../bourbon/bourbon"

Moving it back in so the path was just "bourbon/bourbon" fixed the issue. But as Nuget places it outside by default its no a realistic solution for me.

darrenkopp commented 10 years ago

Alright, I'll look into it. You use compass correct?

funzeye commented 10 years ago

No, Bourbon.

On 20 January 2014 17:10, Darren Kopp notifications@github.com wrote:

Alright, I'll look into it. You use compass correct?

— Reply to this email directly or view it on GitHubhttps://github.com/darrenkopp/SassyStudio/issues/45#issuecomment-32778084 .

David Kivlehan

about.me/funzeye

twitter: @funzeye

mobile: +353872701673

darrenkopp commented 10 years ago

OK, so your IncludePaths has where the bourbon gem is installed and do you have anything in the ruby path (will determine whether sass gem or libsass is being used)?

funzeye commented 10 years ago

Not sure, This is the full error in the compiled css file, mentions libsass so I assume its that?

C:\TFS\HoverCraftStudio\Trunk\HoverCraftStudio\Content\css/imports:9: error: file to import not found or unreadable: "../bourbon/bourbon"

at LibSassNet.SassCompiler.CompileFile(String inputPath, OutputStyle outputStyle, Boolean sourceComments, IEnumerable`1 additionalIncludePaths) at SassyStudio.Integration.LibSass.LibSassNetDocumentCompiler.Compile(FileInfo source, FileInfo output) at SassyStudio.Editor.GenerateCssOnSave.GenerateCss(DateTime time, String path)*/

On 20 January 2014 17:22, Darren Kopp notifications@github.com wrote:

OK, so your IncludePaths has where the bourbon gem is installed and do you have anything in the ruby path (will determine whether sass gem or libsass is being used)

— Reply to this email directly or view it on GitHubhttps://github.com/darrenkopp/SassyStudio/issues/45#issuecomment-32779222 .

David Kivlehan

about.me/funzeye

twitter: @funzeye

mobile: +353872701673

darrenkopp commented 10 years ago

So, it seems like this is a problem in libsass, though I'm not sure why it's a problem... but it worked for me when I did "..\bourbon/bourbon". I'll file a ticket with libsass project. sorry this took me so long to get to.