Closed jakelauer closed 7 years ago
Hello, Jake!
Have you read the documentation?
Quote from documentation:
It should also be noted, that this library does not write the result of compilation to disk.
Compile
andCompileFile
methods of theSassCompiler
class return the result of compilation in the form of an instance of theCompilationResult
class.
The reason I posted was because it allows you to specify an outputPath, which doesn't appear to actually do anything.
Quote from documentation:
outputPath
(optional) - path to output CSS file. Needed for generation of source map. If path to output file is not specified, but specified a path to input file, then value of this parameter is obtained by replacing extension in the input file path by.css
extension.
outputPath
is not my invention. See a original libSass.
Problem is that you do not want to read the documentation.
I see - I did not know that this was part of the original libSass stuff. It was not clear from the documentation that the outputPath did not actually specify the location that files would be created. I now understand that the reason it is used is to identify the location of the source map.
I have set up a build step to use this library to build my SCSS files. It successfully finds all my SCSS files, and the result from the compilation shows their contents, but no files are actually output to the folder. Is there a special setting I need, or a folder permission perhaps?
Here is the code to build them:
` using System; using System.IO; using LibSassHost; using LibSassHost.Helpers;