Chapters

18 Chapters | 1:11:28 |

01

Your First Gulp

4:31
02

Sass to CSS

4:46
03

Sourcemaps

2:46
04

Watch for Changes

3:57
05

Combining (concat) Files

2:57
06

Minify

1:29
07

Minify only in Production

3:04
08

Sourcemaps only in Development

2:04
09

gulp-load-plugins

2:11
10

Errors: Call the Plumber

1:47
11

Page Specific CSS

4:27
12

Bower Components out of web

3:47
13

Minify and Combine JavaScript

6:17
14

Publish Fonts to web

4:10
15

Versioning to Bust Cache

9:10
16

JavaScript Versioning and Cleanup

4:15
17

on('end'): Async and Listeners

6:05
18

Task Order

3:45

This tutorial has a new version, check it out!

> Gulp! Refreshment for Your Frontend Assets

Buy Access to Course

10.

Errors: Call the Plumber

|

Autoplay

Keep on Learning!

If you liked what you've learned so far, dive in! Subscribe to get
access to this tutorial plus video, code and script downloads.

Start your All-Access Pass

Buy just this tutorial for $6.00

Previous Chapter

Next Chapter

Login or register to check out the script

7 Comments

Sort By

Login or Register to join the conversation

Richard 8 years ago

This was one of those real "wow" days. How wonderful is gulp?

|

Victor SFCASTS Richard 8 years ago edited

Hey Richard ,

Haha, we're going to release one more wonderful screencast: Webpack, which is even more wonderful for us, because we've switched from Gulp to Webpack on KnpU about six months ago ;)

Stay tuned!

Cheers!

|

Marouane Rassili 8 years ago

Hi, I'm using @import and partials. When I make a syntax error in one of the partials it doesn't throw an error!! It only throws an error when it detects a syntax error in the main scss file... That's so bad, please help

|

Victor SFCASTS Marouane Rassili 8 years ago

Hey Marouane,

Try to add "use strict" at the top of the JS file, does it help you? See https://www.w3schools.com/j... for more information.

Cheers!

|

Nicolas-S 8 years ago

Hello Ryan,

Just ran into an issue. Plumber seems to prevent gulp to throw the correct exit code when the script fails. It is problematic when you build assets for production in a deployment workflow, and gulp fails silently.

So I now use : .pipe(gulpif(!util.env.production, plumber()))

|

enkuso Nicolas-S 8 years ago

When using plugins, it should be:

.pipe(plugins.if(!config.production, plumber()))

|

weaverryan SFCASTS Nicolas-S 8 years ago

Hey Nicolas!

I like it a lot - very good point. I've added a note at the bottom of this chapter - thanks for sharing!

Cheers!

|

Symfony 2

What PHP libraries does this tutorial use?

// composer.json
{
    "require": {
        "php": ">=5.3.3",
        "symfony/symfony": "2.6.*", // v2.6.4
        "doctrine/orm": "~2.2,>=2.2.3", // v2.4.6
        "doctrine/doctrine-bundle": "~1.2", // v1.2.0
        "twig/extensions": "~1.0", // v1.2.0
        "symfony/assetic-bundle": "~2.3", // v2.5.0
        "symfony/swiftmailer-bundle": "~2.3", // v2.3.7
        "symfony/monolog-bundle": "~2.4", // v2.6.1
        "sensio/distribution-bundle": "~3.0", // v3.0.9
        "sensio/framework-extra-bundle": "~3.0", // v3.0.3
        "incenteev/composer-parameter-handler": "~2.0", // v2.1.0
        "hautelook/alice-bundle": "~0.2" // 0.2
    },
    "require-dev": {
        "sensio/generator-bundle": "~2.3" // v2.4.0
    }
}

Previous Chapter

Next Chapter