Thanks to #853 now the gulp-uncss plugin gets called at the right place, namely inside the styles task instead of the html task. But the problem is now that it cuts off too much from the used css. Compare the two sceenshots below:
With gulp-uncss
Without gulp-uncss
The difference is reflected through the content of ./tmp/styles/main.css.
Another possible solution (compared to what this PR proposes) could be the ignore option which would solve the issue by the Material Design Lite here, but is not a general solution for people using web-starter-kit for their own used libraries, like Angular Material Design etc.
I'm actually now fine with us dropping use of UnCSS in WSK. It exists as a plugin should folks want to manually add it in, but in terms of complexity it's a little OTT for the average user.
Thanks to #853 now the
gulp-uncss
plugin gets called at the right place, namely inside thestyles
task instead of thehtml
task. But the problem is now that it cuts off too much from the used css. Compare the two sceenshots below:gulp-uncss
gulp-uncss
The difference is reflected through the content of
./tmp/styles/main.css
.Another possible solution (compared to what this PR proposes) could be the ignore option which would solve the issue by the Material Design Lite here, but is not a general solution for people using web-starter-kit for their own used libraries, like Angular Material Design etc.
/cc @addyosmani