From 59fcd6c7366b4086886310483abe4f61c8c0de82 Mon Sep 17 00:00:00 2001 From: Cole Chamberlain Date: Wed, 19 Apr 2017 21:53:06 -0700 Subject: [PATCH] Fixed spelling. --- content/api/plugins/compiler.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/api/plugins/compiler.md b/content/api/plugins/compiler.md index 236e169fe912..701d4cb86e0a 100644 --- a/content/api/plugins/compiler.md +++ b/content/api/plugins/compiler.md @@ -51,7 +51,7 @@ Most user facing plugins are first registered on the `Compiler`. The working of a Compiler can be condensed into the following highlights - Usually there is one master instance of Compiler. Child compilers can be created for delegating specific tasks. - A lot of the complexity in creating a compiler goes into populating all the relevant options for it. - - `webpack` has [`WebpackOptionsDefaulter`](https://github.com/webpack/webpack/blob/master/lib/WebpackOptionsDefaulter.js) and [`WebpackOptionsApply`](https://github.com/webpack/webpack/blob/master/lib/WebpackOptionsApply.js) specifically designed to provide the `Compiler` with all the intial data it requires. + - `webpack` has [`WebpackOptionsDefaulter`](https://github.com/webpack/webpack/blob/master/lib/WebpackOptionsDefaulter.js) and [`WebpackOptionsApply`](https://github.com/webpack/webpack/blob/master/lib/WebpackOptionsApply.js) specifically designed to provide the `Compiler` with all the initial data it requires. - The `Compiler` is ultimately just a function which performs bare minimum functionality to keep a lifecycle running. It delegates all the loading/bundling/writing work to various plugins. - `new LogPlugin(args).apply(compiler)` registers the plugin to any particular hook event in the `Compiler`'s lifecycle. - The `Compiler` exposes a `run` method which kickstarts all compilation work for `webpack`. When that is done, it should call the passed in `callback` function. All the tail end work of logging stats and errors are done in this callback function.