Now that we've bootstrapped our application, we might want to add some type of module dependency to our loader, to the node-webkit app, to make our lives much, much easier. We have this bundle.js, and what I'd like to do is actually add webpack to the project, for one because it's awesome, and two, because it's going to make our lives much, much easier.
We need to move this bootstrap material into an index.js or some type of starter file so that webpack can load it and bundle it for us instead of us having it in the bundle file. We are going to create a new file. We're going to call it index.js, and we're just going to move what we have in here into that file. We're going to take everything out, put everything in here and save it. That's cool.
Webpack uses a file called webpack.config.js that is loaded from the root of our project. We're going to go ahead and create that now so we can configure the webpack, how it loads all the dependencies.
Now that we have this file, I'm going to go ahead and copy and paste my standard webpack setup into this file. Here it is. There are a couple of things to note here before we get deep into what's going on. Now, there are other tutorials on Egghead that cover webpack, and I highly recommend you watch them to really get a better idea of how webpack works, but I will give a cursory glance at each of these items here.
It loads things like common JS that users require, which is great, I love that. However, so does node-webkit. So, there's going to be a conflict between these two requires, because node-webkit has its own module dependency loader as well.
We need to actually tell Node Webpack that we're targeting node-webkit. Did I say node webpack? Well, whatever. We're going to target node-webkit, and then the webpack in the background will do some magic to make it compatible with node-webkit, that's pretty important.
Then we have these loaders here. Now, one of the things we need to do is we need to actually install webpack to make this work. We do that just by going NPMI, webpack, and then saving it to our package JSON. We're going to go ahead and install that, and you'll notice that there's a bunch of these loaders in here.
I use these things called loaders. It's going to look at the extension of whatever it is you're trying to require, and then use the loader to bundle it into your application. These loaders here generally do need to be MPM installed as well. I have most of them installed globally, such as this Babel loader, so I'm not going to install each of these individually, but keep in mind the next step.
When we're actually trying to run webpack, if you run into cannot find module, then you just need to install it. That's what we're going to do. We're actually going to run webpack and see how this magic works. You run webpack just by typing webpack into the root of the directory where that webpack config is, but we're actually going to add a flag to watch our files.
It'll compile it anytime a file is changed. We are going to go ahead and watch it right now, and see what happens to this bundle. We're going to look at the bundle, and now we see that it is a webpack bundle. In the webpack bundle, we already have our GUI stuff being set up, and our developer menu should actually work.
We're going to go ahead and run our original application, and see if everything is hunky dory. Sure enough, it is. We have our hello, and we have our develop toggle menu. That's how we do webpack.