2014
02.26

This screencast provides an introduction to the Grails Asset-Pipeline plugin for managing and processing static assets like JavaScript and CSS. The Asset-Pipeline plugin is an alternative to the Resources plugin and it is now installed by default starting with Grails 2.4. Thanks for watching!

6 comments so far

Add Your Comment
  1. Nice screen cast.

    One question though:
    If you have a large javascript library for a specific page, isn’t it a waste loading that on all pages? How would you go about that?

  2. @Søren Thanks, glad you liked it! If you want to load JavaScript files only on select pages, you can just use the asset taglib in those specific GSPs (<asset:javascript src=”someLib.js”/>).

  3. Nice, I just noticed the references to asset-pipeline in a test app I was throwing together with grails 2.3.6 – so this screencast is very timely. This looks very cool, should make tweaking Bootstrap much simpler.

  4. Bobby, the plugin looks great. Am currently using Yeoman, bower and grunt for alot of this. Having much that supported directly within Grails as a plugin is much more convenient. Quick question – will you ever be getting compiler support for TypeScript?

  5. Nice presentation.
    What about single page apps with hundreds of JavaScript files? Should I continue using something like Google Closure / Browserify for creating my minified files or can the Asset Pipeline enable JavaScript files to define which files they are also dependent on?

  6. Bobby,
    what’s your opinion of using gsp or in developing with a front-end like Angularjs and grails in the back?

    thanks,

*

Switch to our mobile site