Control Add-ins Supercharged: Teaching gulp some useful tricks

My last demo introduced gulp, an amazingly simple task automation tool. You’ve seen what it is, how to set it up, and how to create a simple hello-world task. Now it’s time to teach gulp some useful tricks and make it automate the “build” process for the JavaScript and CSS files.

The first demo in this series used a single-file approach, and there I stated that it’s a bad thing to develop like that. It’s bad to put all the functionality in one single file. However, that rule applies for development, not for runtime. Your browser actually prefers using a smaller number of JavaScript (or CSS) files. That’s why typical runtime JavaScript libraries are bundled. On top of bundling, you’ll also want to minify your JavaScript and CSS files to make them as small as possible, to further improve the download and initialization speed.

These are the things that today’s demo uses. So, head over to the branch, and check out how to configure your gulp to build your JavaScript and CSS bundles from your source files.


Read this post at its original location at, or visit the original blog at 5e33c5f6cb90c441bd1f23d5b9eeca34

The post Control Add-ins Supercharged: Teaching gulp some useful tricks appeared first on

Comment List