This week we finished up our e-commerce group projects on Wednesday and then started a short solo hackathon sprint. I decided to explore a machine learning API called Clarifai to build an app that can recognize houses, faces, and houses that look like they have faces. It’s not quite done yet, so more on that later.
I started this project using boilerplate code, and I realized that there was a lot of magic going on behind the scenes that I didn’t fully understand. Generally, I knew what all of the different libraries were doing (Travis was doing something with testing before deploy, webpack was bundling code, etc.) I’ve decided to investigate each of these libraries that I came across a bit more deeply, because I want to be able to provide more eloquent explanations of the tools I’m using to support my code.
First up: the mysterious Webpack.
- Webpack is a static module bundler. Modules are chunks of functionality. Imagine that my packing list is on my computer and I’m using links to other, smaller packing lists that live elsewhere. Let’s say that my Clothes packing list module includes a link to a Beachwear list, some items I’ve just typed in, and another link to a Hiking list. The bundle created would include all of the other lists referenced, which are called dependencies. Bundling allows the browser to load fewer chunks of information in order to display your app – instead of having to click through to see all of these packing lists, it just gets one master list to display.
- The webpack entry point is like saying, ‘Hey application! I’m gonna give you some bundled instructions, and to do them, you gotta start at the Clothes part of the list.” Webpack defaults to using ./src/index.js as its entry point, just like I default to starting by packing clothes first. Both of us are flexible if given other specific instructions. Maybe you’d prefer to start packing your makeup first.
- The webpack output is like saying, ‘Hey application! I made you all these nice instructions on how to pack for your trip, and I’m putting them all together in a list named [something].bundle.js. Webpack defaults to ./dist/main.js, but again, that can be changed in the config file.
There are other components of webpack that I haven’t touched on here, but going through the basics and comparing them to my imperfect-but-helpful packing example definitely makes me more clear about what webpack is doing with my application. It’s essentially a streamlining tool that takes a whole mess of files that all reference each other and creates a simpler, fewer-layer to do list for the browser to implement.