Skip to content

Commit 16800d6

Browse files
Dasari Joel SriprakashDasari Joel Sriprakash
authored andcommitted
docs(output): fix review feedback
1 parent 3772854 commit 16800d6

1 file changed

Lines changed: 2 additions & 4 deletions

File tree

src/content/configuration/output.mdx

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -219,11 +219,9 @@ export default {
219219

220220
The global variable used by webpack for loading chunks asynchronously (e.g. via code splitting and dynamic `import()`).
221221

222-
In webpack 4, this was called `output.jsonpFunction`.
223-
224222
**Why does this matter?**
225223

226-
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:
224+
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:
227225
```
228226
TypeError: webpack_modules[moduleId] is not a function
229227
```
@@ -239,7 +237,7 @@ export default {
239237
};
240238
```
241239

242-
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.
240+
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.
243241

244242
## output.chunkLoading
245243

0 commit comments

Comments
 (0)