Why vendor.css takes the highest level

[roeliman]

I love this generator for its simplicity since booststrap 3 version. but when update come, it's got me frustrated i try to change background color of the body on main,css to black but the browser still put white color on vendor.css as the highest level

please help me :(

why its happen?

[roeliman]

important property is not a a solution how to make my main css to be the first level css i already put main.css on the top on html structure, but it goes nothing

[silvenon]

Thanks for spotting this. Place vendor.css comment block before your main.css block and things should be fine. See f2624c4c79b4ab188267dccbd8d0965201428f59 for reference. (This has been fixed now in the latest prerelease.)

[roeliman]

wow it did worked thanks @silvenon

one more question, on previous version yeoman use bower, but now its not using bower anymore? here's the thing, when i use bower, everytime i install new package, slick for example bower will automatically add the dependecy slick file into html. like css and js file on bower.json

can we do that on this yeoman version? coz, now i have to add manually the css and js file

[silvenon]

Yeah, I liked that too, but Bower has been deprecated so we had to remove it sooner or later. The tool that was automatically injecting dependencies in your HTML file was wiredep, but it only works for Bower. For now you'll have to add dependencies manually because this is not possible to do automatically with npm, but we'll see if we can remedy this downgrade down the road with Parcel.

[roeliman]

that's a wise decision, i have to used to it thanks for your great job

[silvenon]

Thanks!