Jump to content

Guard as my new preprocessor/concat/minify watch tool


owzim
 Share

Recommended Posts

I just switched form CodeKit to Guard. I have more control over how things work, it’s cross platform and more team friendly, and it's free.

Might be worth a look for you guys as well:

"Guard is a command line tool to easily handle events on file system modifications."

https://github.com/guard/guard

Here's a nice intro by Jeffrey Way on Nettuts+

http://net.tutsplus.com/tutorials/tools-and-tips/guard-is-your-best-friend/

Cheers

  • Like 3
Link to comment
Share on other sites

Hello,

I'll take a look at this.

For some reason, I have never really been able to get into SASS or LESS, and I tend to keep building CSS as CSS.  But I always feel I am missing something, as everyone else seems to be using a pre-processor.  Maybe something like Guard will motivate me?

I suppose if I wait long enough, at least some of the pre-processor actions will become part of the CSS spec!

Thanks,

Matthew

  • Like 1
Link to comment
Share on other sites

*grunts*

Grunt.js seems too complicated for me, haven't got the hang of it yet. Though, it might be very powerful. I'll for now stick with Guard and might check out Grunt in a month or two =)

And Grunt.js is not preprocessing, right? It's a build tool, so how would you use Grunt for compiling Sass, Less and CoffeeScript while developing?

Link to comment
Share on other sites

Grunt.js seems to complicated for me, haven't got the hang of it yet. Though, it might be very powerful. I'll for now stick with Guard and might check out Grunt in a month or two =)

And Grunt.js is not preprocessing, right? It's a build tool, so how would you use Grunt for compiling Sass, Less and CoffeeScript while developing?

There you go http://gruntjs.com/plugins

Link to comment
Share on other sites

And Grunt.js is not preprocessing, right? It's a build tool, so how would you use Grunt for compiling Sass, Less and CoffeeScript while developing?

You would have Sass (and/or Compass or whatever you prefer) installed and let your Grunt build script's watch task run it for you in the background. For me that's just it: Grunt can do so much more than just run a preprocessor. Yes, it needs some time to get into and get the hang of it, but once you've set up your Grunt tasks, it does practically everything but write code.

And I'm sure the Grunt guys are going to figure that out as well one day.  ;)

  • Like 1
Link to comment
Share on other sites

  • 3 weeks later...

*grunts*

Finally grunt-contrib-watch implemented livereload natively so that it can be used without any hassle. Tried previous solutions with the grunt-contrib-livereload in conjunction with regard and connect but could not make it work. Now it works like a charm.

http://stackoverflow.com/questions/16371022/how-to-use-grunt-contrib-livereload

So yet again, workflow replaced, Guard is yesterday =D

  • Like 1
Link to comment
Share on other sites

I think grunt is close to the most interesting thing happening around the organization of frontend projects. While it is certainly great that it can do the dirty and boring work for you, it also really looks like us web developers finally have an open, stable and really flexible way of sharing our process. I have the feeling that with all the projects on Github that use it now, grunt had really come to stay, so it's definitely worth a look for everyone working with the web stack.

  • Like 1
Link to comment
Share on other sites

  • 8 months later...
  • 1 year later...
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...