v0.3.5

Fixed issue #4
Adopted for laravel-elixir 6.0.0-3

v0.3.3

Changes in current release

• Completely rewritten versioning system to avoid conflicts with native version task.
• Added option to manually enable versioning in production mode (by default: false)
• Fixed couple of bugs

Example gulpfile.js

const 
    elixir = require('laravel-elixir'),
    config = elixir.config;

config.assetsPath = 'project/assets';
config.publicPath = 'project/public';

// New custom option (works only with current elixir-plugin)
config.versioning.enabled = true;

// Require webpack-advanced plugin
require("laravel-elixir-webpack-advanced");

// Executing bunch of tasks
elixir(mix => {

    mix
        .sass('styles.scss')

        /*
         * -- Optional task
         *
         * Native version task should be triggered before webpack, 
         * otherwise `version` will clear webpack's records in rev-manifest.json
         */
        .version('css/styles.css')
        .webpack('app.js', {
            output: {
                publicPath: `/public/${config.js.outputFolder}/`
            }
        });

});

Then start in production mode:

gulp --production

All changes will be reflected in Readme soon