From 8cccd9a927ac9e301c991ac311fe677451b7e08d Mon Sep 17 00:00:00 2001 From: Simon Legner Date: Tue, 20 Jun 2017 09:22:23 +0200 Subject: [PATCH] docs(config/node): add `false` for `node` option --- content/configuration/node.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/content/configuration/node.md b/content/configuration/node.md index d9534a4233c3..059a94055fd3 100644 --- a/content/configuration/node.md +++ b/content/configuration/node.md @@ -17,7 +17,7 @@ These options configure whether to polyfill or mock certain [Node.js globals](ht This is an object where each property is the name of a Node global or module and each value may be one of the following... - `true`: Provide a polyfill. -- `"mock"`: Provide a mock that implements the expected interface but has little or no fuctionality. +- `"mock"`: Provide a mock that implements the expected interface but has little or no functionality. - `"empty"`: Provide an empty object. - `false`: Provide nothing. Code that expects this object to be defined may crash. @@ -37,6 +37,8 @@ node: { } ``` +Since webpack 3.0.0, the `node` option may be set to `false` to turn off the `NodeSourcePlugin` completely. + ## `node.console`