Download
At its core, webpack is a static module bundler for modern JavaScript applications. When webpack processes your application, it internally builds a dependency graph from one or more entry points and then combines every module your project needs into one or more bundles, which are static assets to serve your content from. Now that we've covered much of the backlog of missing documentation, we are starting to heavily review each section of the site's content to sort and structure it appropriately. Since version 4.0.0, webpack does not require a configuration file to bundle your project. Nevertheless, it is incredibly configurable to better fit your needs. This document is intended to give a high-level overview of these concepts, while providing links to detailed concept-specific use cases. An entry point indicates which module webpack should use to begin building out its internal dependency graph.
Features
- Guides, documentation, and all things webpack
- The output property tells webpack where to emit the bundles it creates and how to name these files
- You can configure this part of the process by specifying an output field in your configuration
- Out of the box, webpack only understands JavaScript and JSON files
- Loaders allow webpack to process other types of files and convert them into valid modules
- While loaders are used to transform certain types of modules, plugins can be leveraged to perform a wider range of tasks
Project Samples
