From 17b7637bec6786a5cfbdd680f07a7727d608e4b9 Mon Sep 17 00:00:00 2001 From: Rupendra0 Date: Tue, 11 Nov 2025 12:26:46 +0530 Subject: [PATCH 1/2] docs: fix duplicate word typos in documentation Fixed two instances of duplicate words: - 'the the' 'the' in module-variables.mdx - 'a a' 'as a' in module.mdx These typos affected readability and professionalism of the documentation. --- src/content/api/module-variables.mdx | 2 +- src/content/configuration/module.mdx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/src/content/api/module-variables.mdx b/src/content/api/module-variables.mdx index 73f69a073908..7b24630569ee 100644 --- a/src/content/api/module-variables.mdx +++ b/src/content/api/module-variables.mdx @@ -219,7 +219,7 @@ import('./module-a').then((moduleA) => { -It provides access to the the current `module`. `module` is not available in strict ESM. +It provides access to the current `module`. `module` is not available in strict ESM. ## \_\_webpack_module\_\_.id (webpack-specific) diff --git a/src/content/configuration/module.mdx b/src/content/configuration/module.mdx index 70b69b0d6f78..54a2ef184945 100644 --- a/src/content/configuration/module.mdx +++ b/src/content/configuration/module.mdx @@ -1244,7 +1244,7 @@ module.exports = { }; ``` -When used a a function, it executes for every module and must return a data URI string. +When used as a function, it executes for every module and must return a data URI string. ```js module.exports = { From afbb0b1931a470ac9c0d8125ad3b829c53fe1429 Mon Sep 17 00:00:00 2001 From: Rupendra0 Date: Tue, 11 Nov 2025 18:47:20 +0530 Subject: [PATCH 2/2] Fix typo: syncronously -> synchronously in getting-started guide --- src/content/guides/getting-started.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/guides/getting-started.mdx b/src/content/guides/getting-started.mdx index da7b53617d63..79ef48512356 100644 --- a/src/content/guides/getting-started.mdx +++ b/src/content/guides/getting-started.mdx @@ -201,7 +201,7 @@ Now, since we'll be bundling our scripts, we have to update our `index.html` fil ``` -T> A couple other script loading strategies exist. Deferred loading is one such alternative to the above, where instead scripts are consolidated into the `` and are given the `defer` attribute. This strategy downloads the external script resource(s) in parallel with document parsing, and will execute the scripts in order of document appearance after parsing has finished. This is in contrast to the above, in which the parser pauses to download and then execute the external resource syncronously. To learn more about this process, MDN has a nice [`reference guide`](https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/script#async_and_defer). +T> A couple other script loading strategies exist. Deferred loading is one such alternative to the above, where instead scripts are consolidated into the `` and are given the `defer` attribute. This strategy downloads the external script resource(s) in parallel with document parsing, and will execute the scripts in order of document appearance after parsing has finished. This is in contrast to the above, in which the parser pauses to download and then execute the external resource synchronously. To learn more about this process, MDN has a nice [`reference guide`](https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/script#async_and_defer). In this setup, `index.js` explicitly requires `lodash` to be present, and binds it as `_` (no global scope pollution). By stating what dependencies a module needs, webpack can use this information to build a dependency graph. It then uses the graph to generate an optimized bundle where scripts will be executed in the correct order.