Enhance documentation for output.chunkLoadingGlobal

Clarify the usage and importance of output.chunkLoadingGlobal in webpack configurations.

Author: joeldasari

src/content/configuration/output.mdx

@@ -213,24 +213,34 @@ export default {
 };
 ```
 
-## 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**
+In webpack 4, this was called `output.jsonpFunction`.
 
-```javascript
+**Why does this matter?**
+
+When multiple independent webpack builds are loaded on the same page, 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 on the same page.
+
 ## output.chunkLoading
 
 `false` `string: 'jsonp' | 'import-scripts' | 'require' | 'async-node' | 'import' | <any string>`