Looking for maintainers, I no longer do much if any PHP dev, I have moved on, mostly work in dotnet core, node.js & golang these days. If anyone is keen to take over these projects, get in touch - [email protected]

The Asset Gear

An Asset Minification Pipeline for the Robo Task Runner.

How to Install

Installation via composer is easy:

composer require gears/asset

How to Use

The first thing is that I make an assumption you know what the Robo Task Runner is and how the basics of it work. If this is not you, please head over to the robo website and familiarise yourself: http://robo.li/

In your RoboFile.php you need to import the Gears\Asset\loadTasks trait like so:

class RoboFile extends Robo\Tasks
{
    use Gears\Asset\loadTasks;
}

Asset Destination

The very first argument you must supply is the final destination of the asset you are building. This can either be a relative path to the current working directory or an absolute path.

$this->taskBuildAsset('/where/do/you/want/me');

Asset Type

The task is smart and will detect what sort of asset you are trying to build based on file extensions. It goes without saying that you CAN NOT MIX asset types in one build task.

For example this is invalid:

$this->taskBuildAsset('script.js')->source('styles.css')->run();

Asset Source

The task needs to know what source files will be used to build the final asset.
You can supply the source files in a number of ways.

• Single Source File:
  The simplest asset is one which has only one source file. All this would do is run unbuilt.js through the configured Js Minifier.

  $this->taskBuildAsset('built.js')->source('unbuilt.js')->run();

• Single Source Folder:
  Instead of a source file you can define a folder. The task will search for files in the folder that have the same extension as the destination file.

  $this->taskBuildAsset('built.css')->source('/my/styles')->run();

  NOTE: Files inside folders are sorted by name. So you could manipulate the order that files are concatenated together by prefixing a numeric index to each source file.

• Many Sources:
  You can supply any array of source files and/or folders.

  $this->taskBuildAsset('built.js')->source
  ([
      '/js/jquery.js',
      '/js/jquery/plugins',
      '/js/main.js'
  ])->run();

• Symfony Finder:
  The last option is to supply your own configured Finder instance.

  $this->taskBuildAsset('built.js')
  ->source
  (
      (new Finder)
        ->files()
          ->in('/path/to/assets')
          ->name('*.js')
          ->sortByName()
  )
  ->run();

  For documentation on the Finder refer to: http://symfony.com/doc/current/components/finder.html

Css Transpilation:

The task supports transpiling both Less and Scss to Css.

If are building a css asset, this happens automatically for you. Any of your source files that are detected with a less or scss file extension will be transpiled with either:

• less.php
• scssphp

NOTE: You can not supply a folder of less or scss files. If you did have a folder of such source files you could configure a Finder instance to find those files. Each file would be transpiled in isolation and then the output concatenated.

Js Transpilation:

To save any future questions, I don't believe there is any point in supporting say TypeScript or Babel simply because, to run both of those transpiliers you must have node installed.

And if you have node, and you are programming in TypeScript or ES6 then chances are you will probably already be using some sort of js bundler.

UPDATE 2017-03-16: Came across an intresting project v8js. This could be used to run things like babel in a purely PHP environment. Checkout php-babel-transpiler.

However due to the installation barrier of the plugin (having to dick around with compilations of v8, etc) it seems like it would just be easier to use node.js directly.

Docker may provide a solution to the install problem but the projects that use this package (mostly wordpress sites) arn't running on docker yet and probably never will.

As much as I would like to turn this into the ultimate asset build pipeline for PHP in 2017, the fact is that it just makes more sense to use the tools that are designed for frontend builds directly instead of trying to shoehorn them into the PHP ecosystem.

Thus this package will remain as is and provide an older style, yet muture & simple asset build pipeline. If a project called for anything fancy like ES6, TypeScript or React then there are other tools like Browserify, Webpack & RollupJs that will do a much better job than anything built in PHP.

Options

• Debug:
  By default the task will always minify your css or js asset. If you wish to only build the asset, which will just concatenate the source files. You can set debug to true like this:

  $this->taskBuildAsset(...)->source(...)->debug(true)->run();

• Gz:
  Optionally the task can create a gzipped version of the final asset. This is so that web servers can be configured to server the pre gzipped version of the file instead of gzipping the file on the fly.

  $this->taskBuildAsset(...)->source(...)->gz(true)->run();

• AutoPrefix:
  If building a css asset, the task will automatically run a css autoprefixer before outputting the file. Autoprefixing parses CSS and adds vendor prefixes to CSS rules using values from http://caniuse.com/

  For more info see: https://github.com/vladkens/autoprefixer-php

  To turn this feature off:

  $this->taskBuildAsset(...)->source(...)->autoprefix(false)->run();

• Template:
  This is a cache busting feature. If you provide a valid file path to a HTML template. The task will then save the final asset with the current unix time-stamp between it's base name and it's extension.

  For example: script.1456298250.js

  It will then search and replace the template file for any references to the asset. The task is smart and uses a regular expression. So if your template contained the asset name without the time-stamp or it contained the asset name with a previously built time-stamp it will still update the reference.

  $this->taskBuildAsset(...)->source(...)->template('view.html')->run();

  NOTE: The template does not have to strictly be a HTML file. It could be any text based file. So it will work just fine with view frameworks like Laravel Blade, Twig, Plates, Foil, etc.

---

Developed by Brad Jones - [email protected]