Web::AssetLib - Moose-based pluggable library manager for compiling and serving static assets
Create a library for your project:
Compile assets from that library:
Web::AssetLib allows you to build an easy-to-tweak input -> (minfiy) -> output pipeline for web assets, as well as a framework for managing those assets.
Possibilities for future plugins: Amazon S3 output, other CDN outputs, SASS input, etc.
This documentation uses method signature notation as defined by Method::Signatures.
Basic usage is covered in Web::AssetLib::Library.
The following base classes are provided for extendability:
Web::AssetLib::Library — a base class for writing your own asset library, and configuring the various pipeline plugins
Web::AssetLib::InputEngine — a base class for writing your own Input Engine
Web::AssetLib::OutputEngine — a base class for writing your own Output Engine
Web::AssetLib::MinifierEngine — a base class for writing your own Minifier Engine
The following objects are used to define assets or groups of assets:
Web::AssetLib::Asset — a representation of a particular asset in your library
Plugins provided by default:
Web::AssetLib::InputEngine::LocalFile — allows importing an asset from your local filesystem
Web::AssetLib::InputEngine::RemoteFile — allows importing an asset via a URL
Web::AssetLib::InputEngine::Content — allows importing an asset as a raw string
Web::AssetLib::OutputEngine::LocalFile — allows exporting an asset or bundle to your local filesystem
Please report any bugs or feature requests through the issue tracker at https://github.com/ryan-lang/Web-AssetLib/issues. You will be notified automatically of any progress on your issue.
This is open source software. The code repository is available for public review and contribution under the terms of the license.
git clone https://github.com/ryan-lang/Web-AssetLib.git
Ryan Lang <email@example.com>