Using Grunt and Bower with Lift
I’m very grateful that I always get a chance to work with very smart people, and I get the chance to learn new tools, languages, techniques, etc. Here I’ll talk about Grunt, which Tim Nelson introduced me to. And I’ll talk a bit about Bower and how they can work together to help you in your Lift applications.
What is Grunt?
From the grunt site, they label it as a task runner, and here I use it to run tasks like js hint, minify both, js and css files and a few other things.
The thing I love the most is that I can have a terminal running
jshint and tell me the errors that I normally would only see on the browser after refreshing the page and clicking around to test out the code I just wrote. This saves a lot of time.
What about Bower?
I use bower as a dependency manager, I have a
bower install and you are ready to go.
But Fobo does something similar to bower.
But xyz sbt plugin does that.
I’m sure, but sbt is slow, plugin versions change and it’s a lot of work to track down which dependency works with this or that other plugin, and underneath they still run other commands. I feel that sbt does a good job at scala code (and maybe java, never tried that), but we should use a different set of tools for client side code, and client side developers are being very productive with tools like Grunt (there is also yeoman if you really want to get into this).
The community behind grunt is huge, and that means that most likely what you are trying to do, they already did for you.
So now what?
The one issue I have right now, with the implementation that I use on thie repo is that
grunt watch will not only update the js files you modified,but it will rerun the minification, uglification and concatenation of js files, and this takes time, on my laptop it takes about a second, or maybe a bit more.
A better solution would be to include the files just like we used to, and only run
jshint on the file you just changed, and when you are ready to deploy your app, you would run it in
production mode and then Lift would replace all those
<script src=...</script> tags for just one. I believe this is what Tim has running right now, but I haven’t looked at it yet.
But I didn’t want to delay posting this, I believe that releasing early and often is a good thing, and we can all make this idea better, together.
Thanks for reading, please give the sample app a try and let us know what you think.