With a Gulp task file and associated
package.json file in place, we should be good to go, right? Well, not quite—yes, our processor has been used on demos throughout the book to great effect. But there is more that we can do: our Gulp file should never be static; we should always look to review it periodically, to ensure it is working at optimal efficiency.
To see an updated version of our Gulp file, take a look in the
T49 – fixing issues in Gulpfile folder within the code download that accompanies this book.
Our Gulp file does have a few issues we need to address, so let's look at these now: