Skip to content

docs(config/node): add false for node option #1317

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 20, 2017
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion content/configuration/node.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch, that misspelling didn't read too well 😆

- `"empty"`: Provide an empty object.
- `false`: Provide nothing. Code that expects this object to be defined may crash.

Expand All @@ -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`

Expand Down