What is the role of the asset-pipeline plugin in Grails?

The asset-pipeline plugin manages an application's front-end assets — CSS, JavaScript, images — handling compilation, minification, bundling, and cache-busting so a developer doesn't have to wire up a separate front-end build tool just to get reasonably optimized static assets in production.

During development, assets are typically served unminified and individually for easier debugging; in production, the plugin bundles related files together, minifies CSS and JS, and appends content-based digests to filenames (or query parameters) so browsers reliably pick up a new version after a deployment instead of serving a stale cached copy. Assets are organized under grails-app/assets, and GSP templates reference them through dedicated tags (like <asset:javascript src="..."/>) rather than hardcoded paths, so the plugin can rewrite those references to the correct bundled/versioned output automatically.

This gives a Grails application reasonable front-end asset handling out of the box without requiring a separate, independently-configured JavaScript build toolchain (Webpack, Vite, etc.) for applications whose front-end needs don't go beyond standard CSS/JS bundling.