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.
Note
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:
Some of our tasks are not correctly named—for example, the styles task could be renamed to better reflect that we're using Rucksack in this task.
There is a question about the use of source maps; so far we've used a dedicated source map plugin to create them. An upcoming change in Gulp 4 will reduce the need for a plugin—support for creating them is being added to...