An assetmanager module for Laminas

v3.0.2 2023-07-22 10:03 UTC

This package is auto-updated.

Last update: 2023-09-22 10:15:48 UTC


By Wesley Overdijk and Marco Pivetta

Updated to laminas by Johan van der Heide


This module is intended for usage with a default directory structure of a Laminas Skeleton Application. It provides functionality to load assets and static files from your module directories through simple configuration. This allows you to avoid having to copy your files over to the public/ directory, and makes usage of assets very similar to what already is possible with view scripts, which can be overridden by other modules. In a nutshell, this module allows you to package assets with your module working out of the box.


  1. Require assetmanager:
./composer.phar require jield-webdev/laminas-assetmanager
#when asked for a version, type "1.*".


Sample module config:


return [
    'asset_manager' => [
        'resolver_configs' => [
            'collections' => [
                'js/d.js' => [
            'paths'       => [
                __DIR__ . '/some/particular/directory',
            'map'         => [
                'specific-path.css' => __DIR__ . '/some/particular/file.css',
        'filters'          => [
            'js/d.js' => [
                    // Note: You will need to require the classes used for the filters yourself.
                    'filter' => 'JSMin',
        'view_helper'      => [
            'cache'            => 'Application\Cache\Redis', // You will need to require the factory used for the cache yourself.
            'append_timestamp' => true,                      // optional, if false never append a query param
            'query_string'     => '_',                       // optional
        'caching'          => [
            'js/d.js' => [
                'cache' => 'Apc',

CLI usage:

Based on Laminas-CLI also support for asset warm up and purge is available.

./vendor/bin/laminas assetmanager:warmup --purge|-p --verbose|-v

This script will create all the assets and store them in the cache. If the purge flag is set, it will also purge the existing cache. This can be useful in a deployment scenario.

Please be careful, since this module will serve every file as-is, including PHP code.

The task list has been slimmed down a lot lately. However, there are still a couple of things that should be done.

  • Renewing the cache