Thanks for the kind words. Unfortunately there is not a way to access the compiled output from the back office of Umbraco at this time. There is a preview feature that you can us to view the output but that only works on the main scss file and not the included underscored files, i.e. main.scss and not _mixins.scss.
When you are run in debug mode the main scss file is compile and essentially sent to the browser as a stream so there is not a physical file to open from that back office. When you are not in debug mode Client Dependancy takes that stream and creates a cached version so that it does not have to recompile on every request.
I have thought about adding a feature to compile the scss files and saving the file to say the CSS directory so if you wanted to use the output instead of the HTTP handler it would be an option.
How to access the compiled file from the backend?
Hi Jason,
The package is really good. Is there a way that I can access the compiled CSS file of the SCSS from the umbraco backend itself?
Thanks for the kind words. Unfortunately there is not a way to access the compiled output from the back office of Umbraco at this time. There is a preview feature that you can us to view the output but that only works on the main scss file and not the included underscored files, i.e. main.scss and not _mixins.scss.
When you are run in debug mode the main scss file is compile and essentially sent to the browser as a stream so there is not a physical file to open from that back office. When you are not in debug mode Client Dependancy takes that stream and creates a cached version so that it does not have to recompile on every request.
I have thought about adding a feature to compile the scss files and saving the file to say the CSS directory so if you wanted to use the output instead of the HTTP handler it would be an option.
is working on a reply...