Another way that the application can be improved is through the removal of unwanted code. When automated, this is often called tree shaking, which we will discuss in later chapters. When this is done manually, it is referred to as code linting. A definition is probably in order as it is a phrase that is not often encountered in programming.
Code linting is the process of removing unwanted or surplus code, just like removing lint from a blazer. This could include unused coding artifacts, erroneous code, or anything else that's unwanted. Webpack uses an automated process to do this when integrating with task runners such as Gulp. This is discussed in the following chapter, Chapter 6, Production, Integrations, and Federated Modules.
If you follow these procedures, then there can be little doubt that your application will perform at its very best. Code splitting and modular programming are central to Webpack and a firm understanding is required to prevent you from getting lost as the complexity of bundling projects advances through this guide.