 Hey, are you getting tired of the command line yet? I'm Sarah Clark, and I'm here to show you how to integrate Workbox with a build system. Using a build system ensures that any changes in your app are picked up by Workbox. You can also use this to work with newer versions of JavaScript, compress your site, and more. Last time, we installed Workbox as a command line node module. We ran the wizard, and then generated a service worker with a command. Now we'll take that knowledge and apply it to node, gulp, and webpack. You could write your own command line tool by creating a JavaScript file for node. We only need to load the Workbox build library and then move the values from the configuration file into here. But it's still not a build system. Gulp is a build system. You give it a series of steps to build your app, and it runs whatever is needed to keep your build up to date. It's the same code as you used for node.js but inside a gulp task. That's the beauty of Workbox being a node module. It works with any build system that can run JavaScript or use the command line. Webpack is another popular build system. Workbox supplies a plugin for Webpack, so you can load that instead if you want. Calling generate SW creates a service worker. By default, the plugin pre-caches everything. This matches Webpack's default of collecting all the files in your app. You can copy our custom configuration into Webpack. Here, we're excluding all of the image files from pre-caching so they don't get picked up by default. Instead, they get their own cache. Seriously, that's it. The same configuration code works anywhere you can put JavaScript. Again, the Workbox website should be your first stop for documentation. Try it on a few sites or apps, and you'll pick it up quickly. After that, come on back for more lessons. Thanks for watching and happy caching.