Compiling Assets (Laravel Elixir)

Introduction

Laravel Elixir provides a clean, fluent API for defining basic Gulp tasks for your Laravel application. Elixir supports common CSS and JavaScript pre-processors like Sass and Webpack. Using method chaining, Elixir allows you to fluently define your asset pipeline. For example:

  1. elixir(function(mix) {
  2.     mix.sass('app.scss')
  3.        .webpack('app.js');
  4. });

If you've ever been confused and overwhelmed about getting started with Gulp and asset compilation, you will love Laravel Elixir. However, you are not required to use it while developing your application. You are free to use any asset pipeline tool you wish, or even none at all.

Installation & Setup

Installing Node

Before triggering Elixir, you must first ensure that Node.js and NPM are installed on your machine.

  1. node -v
  2. npm -v

By default, Laravel Homestead includes everything you need; however, if you aren't using Vagrant, then you can easily install the latest version of Node and NPM using simple graphical installers from their download page.

Gulp

Next, you'll need to pull in Gulp as a global NPM package:

  1. npm install --global gulp-cli

Laravel Elixir

The only remaining step is to install Laravel Elixir. Within a fresh installation of Laravel, you'll find a package.json file in the root of your directory structure. The default package.json file includes Elixir and the Webpack JavaScript module bundler. Think of this like your composer.json file, except it defines Node dependencies instead of PHP. You may install the dependencies it references by running:

  1. npm install

If you are developing on a Windows system or you are running your VM on a Windows host system, you may need to run the npm install command with the —no-bin-links switch enabled:

  1. npm install --no-bin-links

Running Elixir

Elixir is built on top of Gulp, so to run your Elixir tasks you only need to run the gulp command in your terminal. Adding the —production flag to the command will instruct Elixir to minify your CSS and JavaScript files:

  1. // Run all tasks...
  2. gulp
  4. // Run all tasks and minify all CSS and JavaScript...
  5. gulp --production

Upon running this command, you'll see a nicely formatted table that displays a summary of the events that just took place.

Watching Assets For Changes

The gulp watch command will continue running in your terminal and watch your assets for any changes. Gulp will automatically recompile your assets if you modify them while the watch command is running:

  1. gulp watch

Working With Stylesheets

The gulpfile.js file in your project's root directory contains all of your Elixir tasks. Elixir tasks can be chained together to define exactly how your assets should be compiled.

Less

The less method may be used to compile Less into CSS. The less method assumes that your Less files are stored in resources/assets/less. By default, the task will place the compiled CSS for this example in public/css/app.css:

  1. elixir(function(mix) {
  2.     mix.less('app.less');
  3. });

You may also combine multiple Less files into a single CSS file. Again, the resulting CSS will be placed in public/css/app.css:

  1. elixir(function(mix) {
  2.     mix.less([
  3.         'app.less',
  4.         'controllers.less'
  5.     ]);
  6. });

If you wish to customize the output location of the compiled CSS, you may pass a second argument to the less method:

  1. elixir(function(mix) {
  2.     mix.less('app.less', 'public/stylesheets');
  3. });
  5. // Specifying a specific output filename...
  6. elixir(function(mix) {
  7.     mix.less('app.less', 'public/stylesheets/style.css');
  8. });

Sass

The sass method allows you to compile Sass into CSS. Assuming your Sass files are stored at resources/assets/sass, you may use the method like so:

  1. elixir(function(mix) {
  2.     mix.sass('app.scss');
  3. });

Again, like the less method, you may compile multiple Sass files into a single CSS file, and even customize the output directory of the resulting CSS:

  1. elixir(function(mix) {
  2.     mix.sass([
  3.         'app.scss',
  4.         'controllers.scss'
  5.     ], 'public/assets/css');
  6. });

Custom Paths

While it's recommended that you use Laravel's default asset directories, if you require a different base directory, you may begin any file path with ./. This instructs Elixir to begin at the project root, rather than using the default base directory.

For example, to compile a file located at app/assets/sass/app.scss and output the results to public/css/app.css, you would make the following call to the sass method:

  1. elixir(function(mix) {
  2.     mix.sass('./app/assets/sass/app.scss');
  3. });

Stylus

The stylus method may be used to compile Stylus into CSS. Assuming that your Stylus files are stored in resources/assets/stylus, you may call the method like so:

  1. elixir(function(mix) {
  2.     mix.stylus('app.styl');
  3. });

{tip} This method's signature is identical to both mix.less() and mix.sass().

Plain CSS

If you would just like to combine some plain CSS stylesheets into a single file, you may use the styles method. Paths passed to this method are relative to the resources/assets/css directory and the resulting CSS will be placed in public/css/all.css:

  1. elixir(function(mix) {
  2.     mix.styles([
  3.         'normalize.css',
  4.         'main.css'
  5.     ]);
  6. });

You may also instruct Elixir to write the resulting file to a custom directory or file by passing a second argument to the styles method:

  1. elixir(function(mix) {
  2.     mix.styles([
  3.         'normalize.css',
  4.         'main.css'
  5.     ], 'public/assets/css/site.css');
  6. });

Source Maps

In Elixir, source maps are enabled by default and provide better debugging information to your browser's developer tools when using compiled assets. For each relevant file that is compiled, you will find a companion .css.map or .js.map file in the same directory.

If you do not want source maps generated for your application, you may disable them using the sourcemaps configuration option:

  1. elixir.config.sourcemaps = false;
  3. elixir(function(mix) {
  4.     mix.sass('app.scss');
  5. });

Working With Scripts

Elixir provides several features to help you work with your JavaScript files, such as compiling ECMAScript 2015, module bundling, minification, and simply concatenating plain JavaScript files.

When writing ES2015 with modules, you have your choice between Webpack and Rollup. If these tools are foreign to you, don't worry, Elixir will handle all of the hard work behind the scenes. By default, the Laravel gulpfile uses webpack to compile Javascript, but you are free to use any module bundler you like.

Webpack

The webpack method may be used to compile and bundle ECMAScript 2015 into plain JavaScript. This function accepts a file path relative to the resources/assets/js directory and generates a single bundled file in the public/js directory:

  1. elixir(function(mix) {
  2.     mix.webpack('app.js');
  3. });

To choose a different output or base directory, simply specify your desired paths with a leading .. Then you may specify the paths relative to the root of your application. For example, to compile app/assets/js/app.js to public/dist/app.js:

  1. elixir(function(mix) {
  2.     mix.webpack(
  3.         './app/assets/js/app.js',
  4.         './public/dist'
  5.     );
  6. });

If you'd like to leverage more of Webpack's functionality, Elixir will read any webpack.config.js file that is in your project root and factor its configuration into the build process.

Rollup

Similar to Webpack, Rollup is a next-generation bundler for ES2015. This function accepts an array of files relative to the resources/assets/js directory, and generates a single file in the public/js directory:

  1. elixir(function(mix) {
  2.     mix.rollup('app.js');
  3. });

Like the webpack method, you may customize the location of the input and output files given to the rollup method:

  1. elixir(function(mix) {
  2.     mix.rollup(
  3.         './resources/assets/js/app.js',
  4.         './public/dist'
  5.     );
  6. });

Scripts

If you have multiple JavaScript files that you would like to combine into a single file, you may use the scripts method, which provides automatic source maps, concatenation, and minification.

The scripts method assumes all paths are relative to the resources/assets/js directory, and will place the resulting JavaScript in public/js/all.js by default:

  1. elixir(function(mix) {
  2.     mix.scripts([
  3.         'order.js',
  4.         'forum.js'
  5.     ]);
  6. });

If you need to concatenate multiple sets of scripts into different files, you may make multiple calls to the scripts method. The second argument given to the method determines the resulting file name for each concatenation:

  1. elixir(function(mix) {
  2.     mix.scripts(['app.js', 'controllers.js'], 'public/js/app.js')
  3.        .scripts(['forum.js', 'threads.js'], 'public/js/forum.js');
  4. });

If you need to combine all of the scripts in a given directory, you may use the scriptsIn method. The resulting JavaScript will be placed in public/js/all.js:

  1. elixir(function(mix) {
  2.     mix.scriptsIn('public/js/some/directory');
  3. });

{tip} If you intend to concatenate multiple pre-minified vendor libraries, such as jQuery, instead consider using mix.combine(). This will combine the files, while omitting the source map and minification steps. As a result, compile times will drastically improve.

Copying Files & Directories

The copy method may be used to copy files and directories to new locations. All operations are relative to the project's root directory:

  1. elixir(function(mix) {
  2.     mix.copy('vendor/foo/bar.css', 'public/css/bar.css');
  3. });

Versioning / Cache Busting

Many developers suffix their compiled assets with a timestamp or unique token to force browsers to load the fresh assets instead of serving stale copies of the code. Elixir can handle this for you using the version method.

The version method accepts a file name relative to the public directory, and will append a unique hash to the filename, allowing for cache-busting. For example, the generated file name will look something like: all-16d570a7.css:

  1. elixir(function(mix) {
  2.     mix.version('css/all.css');
  3. });

After generating the versioned file, you may use Laravel's global elixir helper within your views to load the appropriately hashed asset. The elixir function will automatically determine the current name of the hashed file:

  1. <link rel="stylesheet" href="{{ elixir('css/all.css') }}">

Versioning Multiple Files

You may pass an array to the version method to version multiple files:

  1. elixir(function(mix) {
  2.     mix.version(['css/all.css', 'js/app.js']);
  3. });

Once the files have been versioned, you may use the elixir helper function to generate links to the proper hashed files. Remember, you only need to pass the name of the un-hashed file to the elixir helper function. The helper will use the un-hashed name to determine the current hashed version of the file:

  1. <link rel="stylesheet" href="{{ elixir('css/all.css') }}">
  3. <script src="{{ elixir('js/app.js') }}"></script>

BrowserSync

BrowserSync automatically refreshes your web browser after you make changes to your assets. The browserSync method accepts a JavaScript object with a proxy attribute containing the local URL for your application. Then, once you run gulp watch you may access your web application using port 3000 (http://project.dev:3000) to enjoy browser syncing:

  1. elixir(function(mix) {
  2.     mix.browserSync({
  3.         proxy: 'project.dev'
  4.     });
  5. });