Painless Builds With Elixir

Before we can toy around with Elixir, we first need to install the required tools.

It's never been easy to write and compile Sass (or Less, if you prefer) in a project. Let's go over the details.

When it comes to JavaScript, Elixir provides lots of options! Enjoy using CoffeeScript? No problemo. What about using the latest features that EcmaScript 6 and 7 have to offer? Easy! One line of code will do it.

Elixir offers sourcemap support out of the box. This means, when debugging in the browser, rather than reviewing some foreign compiled script or stylesheet, you can instead dig directly into the original Sass partial, or JavaScript module. How cool is that!?

Manually running gulp can get tedious really fast. Instead, opt for the useful gulp watch command to keep an eye on your files for changes.

Easily, one of the most frequent tasks that you'll need to perform, as part of your build process, is file concatenation. Whether you need to merge some scripts or stylesheets, Elixir makes it a cinch!

If you'd like to trigger your PHPUnit or PHPSpec tests with Gulp, then the gulp tdd Terminal command will be your best friend!

Aggressive caching on your production server is a useful technique to improve the performance of your app. But what about when we want to bust that cache? Do we really have to manually update a querystring on a file path? Nope! There's an easier way.

With a vanilla Gulpfile, hooking into Browserify can be a bit of a pain. It takes lots and lots of research to figure out how to apply the necessary transformations and such. With Elixir, it's as simple as a single method call!

Let's use all the techniques we've learned to build a Gulpfile for a simple, yet typical web application.

What about the situations, where you need to call a custom Gulp task of yours? Or what if you even want to extend Elixir, itself? I'll show you how in this lesson.

Whenever possible, stick with the Elixir conventions. However, sometimes, you have no choice. Maybe you require a different public folder name. Or maybe all of your assets should instead be stored in the "app/assets" directory. In this lesson, you'll learn to override the default configuration.

We reviewed Browsersync in the previous episode, but I want to impress upon you how useful this tool can be, when optimizing your sites for various devices. Wouldn't it be nice if you could, in real-time, review a page's layout for desktops, tablets, and phones? Even better, wouldn't it be cool if they were all in sync with one another?