Enhance documentation for output.chunkLoadingGlobal

.vale/Speciesism/AnimalIdioms.yml

@@ -4,29 +4,29 @@ link: https://doi.org/10.1007/s43681-023-00380-w
 level: warning
 ignorecase: true
 swap:
-  'kill two birds with one stone': accomplish two things at once
-  'killing two birds with one stone': accomplishing two things at once
-  'killed two birds with one stone': accomplished two things at once
-  'beat a dead horse': belabor the point
-  'beating a dead horse': belaboring the point
-  'flog a dead horse': belabor the point
-  'flogging a dead horse': belaboring the point
-  'bring home the bacon': bring home the results
-  'bringing home the bacon': bringing home the results
-  'brought home the bacon': brought home the results
-  'more than one way to skin a cat': more than one way to solve this
-  'many ways to skin a cat': many ways to approach this
-  'let the cat out of the bag': reveal the secret
-  'letting the cat out of the bag': revealing the secret
-  'open a can of worms': create a complicated situation
-  'opening a can of worms': creating a complicated situation
-  'opened a can of worms': created a complicated situation
-  'wild goose chase': pointless pursuit
-  'take the bull by the horns': face the challenge head-on
-  'taking the bull by the horns': facing the challenge head-on
-  'took the bull by the horns': faced the challenge head-on
-  'like shooting fish in a barrel': extremely easy
-  'straight from the horse''s mouth': directly from the source
-  'from the horse''s mouth': from a reliable source
-  'whack-a-mole': recurring problem
-  'whack a mole': recurring problem
+  "kill two birds with one stone": accomplish two things at once
+  "killing two birds with one stone": accomplishing two things at once
+  "killed two birds with one stone": accomplished two things at once
+  "beat a dead horse": belabor the point
+  "beating a dead horse": belaboring the point
+  "flog a dead horse": belabor the point
+  "flogging a dead horse": belaboring the point
+  "bring home the bacon": bring home the results
+  "bringing home the bacon": bringing home the results
+  "brought home the bacon": brought home the results
+  "more than one way to skin a cat": more than one way to solve this
+  "many ways to skin a cat": many ways to approach this
+  "let the cat out of the bag": reveal the secret
+  "letting the cat out of the bag": revealing the secret
+  "open a can of worms": create a complicated situation
+  "opening a can of worms": creating a complicated situation
+  "opened a can of worms": created a complicated situation
+  "wild goose chase": pointless pursuit
+  "take the bull by the horns": face the challenge head-on
+  "taking the bull by the horns": facing the challenge head-on
+  "took the bull by the horns": faced the challenge head-on
+  "like shooting fish in a barrel": extremely easy
+  "straight from the horse's mouth": directly from the source
+  "from the horse's mouth": from a reliable source
+  "whack-a-mole": recurring problem
+  "whack a mole": recurring problem

.vale/Speciesism/AnimalMetaphors.yml

@@ -4,11 +4,11 @@ link: https://doi.org/10.1007/s43681-023-00380-w
 level: warning
 ignorecase: true
 swap:
-  'guinea pig': test subject
-  'sacred cow': unquestioned belief
-  'sacred cows': unquestioned beliefs
-  'scapegoat(?:ed|ing)?': wrongly blamed
-  'dog-eat-dog': ruthlessly competitive
-  'dog eat dog': ruthlessly competitive
-  'rat race': competitive grind
-  'red herring': false lead
+  "guinea pig": test subject
+  "sacred cow": unquestioned belief
+  "sacred cows": unquestioned beliefs
+  "scapegoat(?:ed|ing)?": wrongly blamed
+  "dog-eat-dog": ruthlessly competitive
+  "dog eat dog": ruthlessly competitive
+  "rat race": competitive grind
+  "red herring": false lead

.vale/Speciesism/TechTerminology.yml

@@ -3,11 +3,11 @@ message: "Consider using '%s' instead of '%s'. This technical term has a more pr
 level: suggestion
 ignorecase: true
 swap:
-  'canary deployment': progressive rollout
-  'canary release': progressive rollout
-  'canary test(?:ing)?': incremental testing
-  'monkey[- ]?patch(?:ed|ing)?': runtime patch
-  'duck[- ]?typ(?:ed|ing)': structural typing
-  'dogfood(?:ing)?': self-hosting
-  'eat(?:ing)? (?:your|our|their) own dogfood': self-testing
-  'rubber duck(?:ing)? debugging': talk-through debugging
+  "canary deployment": progressive rollout
+  "canary release": progressive rollout
+  "canary test(?:ing)?": incremental testing
+  "monkey[- ]?patch(?:ed|ing)?": runtime patch
+  "duck[- ]?typ(?:ed|ing)": structural typing
+  "dogfood(?:ing)?": self-hosting
+  "eat(?:ing)? (?:your|our|their) own dogfood": self-testing
+  "rubber duck(?:ing)? debugging": talk-through debugging

src/content/configuration/externals.mdx

@@ -683,7 +683,9 @@ import { createRequire as __WEBPACK_EXTERNAL_createRequire } from "node:module";
 const __webpack_modules__ = {
   // ...
   /***/ 2613: /***/ (module) => {
-    module.exports = __WEBPACK_EXTERNAL_createRequire(import.meta.url)("stream");
+    module.exports = __WEBPACK_EXTERNAL_createRequire(import.meta.url)(
+      "stream",
+    );
 
     /***/
   },

src/content/configuration/output.mdx

@@ -213,24 +213,32 @@
 };
 ```
 
-## output.chunkLoadingGlobal
+### output.chunkLoadingGlobal
 
 `string = 'webpackChunkwebpack'`
 
-The global variable is used by webpack for loading chunks.
+The global variable used by webpack for loading chunks asynchronously (e.g. via code splitting and dynamic `import()`).
 
-**webpack.config.js**
+**Why does this matter?**
 
-```javascript
+When multiple independent webpack builds are loaded in the same browser context, they all default to the same global variable name. This causes conflicts and can produce errors like:
+```
+TypeError: webpack_modules[moduleId] is not a function
+```
+
+To avoid this, assign a unique `chunkLoadingGlobal` to each build:
+
+**webpack.config.js**
+```js
 export default {
-  // ...
   output: {
-    // ...
-    chunkLoadingGlobal: "myCustomFunc",
+    chunkLoadingGlobal: "myAppWebpackChunks",
   },
 };
 ```
 
+T> If you have multiple entry points within a **single** webpack config, they already share the same runtime — no conflict will occur. You only need a unique `chunkLoadingGlobal` when running completely **separate** webpack instances in the same browser context.
+
 ## output.chunkLoading
 
 `false` `string: 'jsonp' | 'import-scripts' | 'require' | 'async-node' | 'import' | <any string>`