When I was asked to write this training book, I realized that very little was known about webpack and its purpose. It is generally something a developer stumbles upon and learns on the job, which can be a very laborious process. There is some documentation on the Webpack.js website as well as a handful of credible resources such as Medium. However, these resources do tend to speak to the reader from the point of view of an expert and I, for one, found this not to be ideal.

Coming from the background of being a lecturer in web development, I have seen how very skilled and intelligent people can have blind spots and knowledge gaps. As a lecturer, I was advised, and also relay the message on, that there are no wrong questions. Many people who have not come from a teaching background might suggest they don't want to speak down to you and would prefer you not ask the wrong questions. We have found this is harmful if a student would rather remain silent over asking questions.

I intend to keep things as simple as possible. I may have failed already using words such as "bespoke", nonetheless, the premise is that all of us have head-slapping moments, where we should have done something, and later on realize what we did wrong. Am I right? Well, it happens to the most brilliant of us. Also, most instructors may be reluctant to talk you through something to the nth degree for fear of patronizing you. The problem being is that there will always be some mundane detail, that the developer thought obvious but could be interpreted more than one way. When I lectured the rule was: "there are no stupid questions", so I hope to prove the necessity of that theory.