nov 25 2014 17:49 Barney Carroll <barney.carr...@gmail.com>: > A task runner like Gulp would be useful for this kind of thing. This guy > wrote an excellent introduction (and starter kit) [0] that covers automated > SASS & Browserify code compilation and filesystem-browser synchronisation. > > I've used Gulp for my last 2 major project for all my development and build > needs. When a *.js file changes, it reads over my code and warns me (in the > console) of any code style deviations or syntax errors, compiles it, tells > the browser to reload it, and runs my unit tests, notifying me of any errors. > When a *.scss file changes, it runs compass, concatenates, minifies, writes > source maps, then tells the connected browsers to reload that particular > resource. > > Using a system like this you could easily chuck in a CSS validation report on > each change after the SCSS compilation but before the browser-prefixing. > There's a plugin that reports back from the W3C service [1] which has been > adapted to Gulp [2]. So much more convenient than asking a technical question > on CSS-D and waiting for the reply back with the link to > http://validator.w3.org/! ;) >
That’s very interesting as I installed Gulp in a more complex framework the other day. I haven’t looked it over yet, as I was mostly interested in the server-side things there. I’ll make sure I check out gulp more thoroughly. Thanks. ______________________________________________________________________ css-discuss [css-d@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
