From 0997751c00ea84ead4e407ce2ae8b4b06186a837 Mon Sep 17 00:00:00 2001 From: bhavya chawla Date: Fri, 25 Jan 2019 22:56:36 +0530 Subject: [PATCH 1/2] fix(configuration): correcting grammar --- src/content/configuration/externals.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/src/content/configuration/externals.md b/src/content/configuration/externals.md index 33e70000fd03..a002b6c6e6d4 100644 --- a/src/content/configuration/externals.md +++ b/src/content/configuration/externals.md @@ -10,9 +10,9 @@ contributors: - zefman --- -The `externals` configuration option provides a way of excluding dependencies from the output bundles. Instead, the created bundle relies on that dependency to be present in the consumer's environment. This feature is typically most useful to __library developers__, however there are a variety of applications for it. +The `externals` configuration option provides a way of excluding dependencies from the output bundles. Instead, the created bundle relies on that dependency to be present in the consumer's environment. This feature is typically most useful to __library developers__, however, there are a variety of applications for it. -T> __consumer__ here is any end user application that includes the library that you have bundled using webpack. +T> __consumer__ here is any end-user application that includes the library that you have bundled using webpack. ## `externals` @@ -117,7 +117,7 @@ This syntax is used to describe all the possible ways that an external library c ### function -It might be useful to define your own function to control the behavior of what you want to externalize from webpack. [webpack-node-externals](https://www.npmjs.com/package/webpack-node-externals), for example, excludes all modules from the `node_modules` directory and provides some options to, for example, whitelist packages. +It might be useful to define your own function to control the behavior of what you want to externalize from webpack. [webpack-node-externals](https://www.npmjs.com/package/webpack-node-externals), for example, excludes all modules from the `node_modules` directory and provides some options too, for example, whitelist packages. It basically comes down to this: @@ -149,7 +149,7 @@ module.exports = { }; ``` -In this case any dependency named `jQuery`, capitalized or not, or `$` would be externalized. +In this case, any dependency named `jQuery`, capitalized or not, or `$` would be externalized. ### Combining syntaxes From f210b06eec4e11c582439f1bc48700046814c069 Mon Sep 17 00:00:00 2001 From: bhavya chawla Date: Sun, 10 Feb 2019 10:48:11 +0530 Subject: [PATCH 2/2] fix(configuration): correcting grammar --- src/content/configuration/externals.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/configuration/externals.md b/src/content/configuration/externals.md index a002b6c6e6d4..996783a34d0d 100644 --- a/src/content/configuration/externals.md +++ b/src/content/configuration/externals.md @@ -10,7 +10,7 @@ contributors: - zefman --- -The `externals` configuration option provides a way of excluding dependencies from the output bundles. Instead, the created bundle relies on that dependency to be present in the consumer's environment. This feature is typically most useful to __library developers__, however, there are a variety of applications for it. +The `externals` configuration option provides a way of excluding dependencies from the output bundles. Instead, the created bundle relies on that dependency to be present in the consumer's environment. This feature is typically most useful to __library developers__, however there are a variety of applications for it. T> __consumer__ here is any end-user application that includes the library that you have bundled using webpack.