SCSS stylesheets aren't included about kss-node HOT 16 CLOSED

I ran into this problem too, discovered here that you have to use the css stylesheet your Sass compiles into as a target if not you get an empty style.css.

from kss-node.

@TenEsan do you use sass to compile .scss -> .css first? Because I don't have any .css files until after I run kss-node, but kss-node itself complains if you tell it to use a stylesheet that doesn't exist yet.

from kss-node.

Yes, I do. Then I parse the compiled screen.css with kss-node using --css.

from kss-node.

I have the same problem. MacOS X 10.9, node 0.10.26. KSS version is 0.3.7.

from kss-node.

I think that request #58 will resolve this problem

from kss-node.

I started using GruntJs to run tasks, now I run the grunt styleguide task with my .scss file as the target. As usual it properly parses all the scss comments but outputs an empty style.css. So after that task I run the grunt sass task on my scss with the the style.css as the destination.

from kss-node.

@ogbaoghene grunt-kss using node-sass as a compiler for Sass and SCSS, but node-kss using sass. My recommendation is if you can, use grunt-kss on your project.

from kss-node.

@lancedikson I currently use grunt-styleguide, will give grunt-kss a try. Thanks.

from kss-node.

@ogbaoghene do you have the same problem with grunt-styleguide? This bug should be repeat with it, because it depends of kss-node.

from kss-node.

@lancedikson Yes, I do experience the same issue. As a workaround, I run the grunt-sass task after the grunt-styleguide task, recompiling my CSS with the style.css file as the destination. So I run two tasks, the first to generate my KSS styleguide and the second for the missing styles.

from kss-node.

@ogbaoghene well, I think grunt-kss will be more comfortable decision, than that you have now. Do you have that issue #68 ?

from kss-node.

This will be fixed by #58. But I'm going to rip out all stylesheet compilation from the 1.0.0 version 2.0.0 version. [edit: the 1.0.0 will be a straight bugfix of the 0.3.7 version.] There's simply too many different workflows to support them all. I can think of 8 different ways of compiling Sass off the top of my head.

from kss-node.

@JohnAlbin I think pulling compilation is a step in the right direction.

from kss-node.

I just fixed this #87. Now when you use --sass [file] -l [include-path], it should generate a stylesheet at public/style.css and include it. I haven't tested it thoroughly because I don't compile my Sass source with kss-node. Please re-open (with additional details) if its still not working properly.

from kss-node.

@JohnAlbin just tested, doesn't fix it, kindly reopen. Thanks for trying though.

from kss-node.

@JohnAlbin I also agree that compilation should be separate, this was something that tripped me up when I started using kss-node.

from kss-node.