From 0aaec337bedbb58b6276da36e894b9380149aec9 Mon Sep 17 00:00:00 2001
From: guardrex <1622880+guardrex@users.noreply.github.com>
Date: Thu, 2 Jan 2025 08:42:01 -0500
Subject: [PATCH 1/6] Prohibition on `<script>` tags for modules

---
 aspnetcore/blazor/includes/js-interop/js-collocation.md        | 3 +++
 .../javascript-interoperability/call-javascript-from-dotnet.md | 1 +
 2 files changed, 4 insertions(+)

diff --git a/aspnetcore/blazor/includes/js-interop/js-collocation.md b/aspnetcore/blazor/includes/js-interop/js-collocation.md
index 4170582bf5cc..e152c3cf2a0b 100644
--- a/aspnetcore/blazor/includes/js-interop/js-collocation.md
+++ b/aspnetcore/blazor/includes/js-interop/js-collocation.md
@@ -152,6 +152,9 @@ export function showPrompt2(message) {
 }
 ```
 
+> [!IMPORTANT]
+> Don't place a `<script>` tag for `JsCollocation2.razor.js` after the [Blazor script](xref:blazor/project-structure#location-of-the-blazor-script). The module is loaded automatically and cached. Adding a `<script>` tag results in the module not loading correctly.
+
 Use of scripts and modules for collocated JS in a Razor class library (RCL) is only supported for Blazor's JS interop mechanism based on the <xref:Microsoft.JSInterop.IJSRuntime> interface. If you're implementing [JavaScript `[JSImport]`/`[JSExport]` interop](xref:blazor/js-interop/import-export-interop), see <xref:blazor/js-interop/import-export-interop#razor-class-library-rcl-collocated-js-is-unsupported>.
 
 For scripts or modules provided by a Razor class library (RCL) using <xref:Microsoft.JSInterop.IJSRuntime>-based JS interop, the following path is used:
diff --git a/aspnetcore/blazor/javascript-interoperability/call-javascript-from-dotnet.md b/aspnetcore/blazor/javascript-interoperability/call-javascript-from-dotnet.md
index 5b8ec9a573d3..12a6e7fc5744 100644
--- a/aspnetcore/blazor/javascript-interoperability/call-javascript-from-dotnet.md
+++ b/aspnetcore/blazor/javascript-interoperability/call-javascript-from-dotnet.md
@@ -623,6 +623,7 @@ In the preceding example:
   * The path segment for the current directory (`./`) is required in order to create the correct static asset path to the JS file.
   * The `{SCRIPT PATH AND FILE NAME (.js)}` placeholder is the path and file name under `wwwroot`.
 * Disposes the <xref:Microsoft.JSInterop.IJSObjectReference> for [garbage collection](xref:blazor/components/lifecycle#asynchronous-iasyncdisposable) in <xref:System.IAsyncDisposable.DisposeAsync%2A?displayProperty=nameWithType>.
+* Don't place a `<script>` tag for the script after the [Blazor script](xref:blazor/project-structure#location-of-the-blazor-script). The module is loaded automatically and cached. Adding a `<script>` tag results in the module not loading correctly.
 
 Dynamically importing a module requires a network request, so it can only be achieved asynchronously by calling <xref:Microsoft.JSInterop.IJSRuntime.InvokeAsync%2A>.
 

From 83375dd625bdd83977d77495adec94a4473932f8 Mon Sep 17 00:00:00 2001
From: guardrex <1622880+guardrex@users.noreply.github.com>
Date: Fri, 3 Jan 2025 05:33:23 -0500
Subject: [PATCH 2/6] Updates

---
 aspnetcore/blazor/includes/js-interop/js-collocation.md         | 2 +-
 .../javascript-interoperability/call-javascript-from-dotnet.md  | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/aspnetcore/blazor/includes/js-interop/js-collocation.md b/aspnetcore/blazor/includes/js-interop/js-collocation.md
index e152c3cf2a0b..48d52fc6d513 100644
--- a/aspnetcore/blazor/includes/js-interop/js-collocation.md
+++ b/aspnetcore/blazor/includes/js-interop/js-collocation.md
@@ -153,7 +153,7 @@ export function showPrompt2(message) {
 ```
 
 > [!IMPORTANT]
-> Don't place a `<script>` tag for `JsCollocation2.razor.js` after the [Blazor script](xref:blazor/project-structure#location-of-the-blazor-script). The module is loaded automatically and cached. Adding a `<script>` tag results in the module not loading correctly.
+> Don't place a `<script>` tag for `JsCollocation2.razor.js` after the [Blazor script](xref:blazor/project-structure#location-of-the-blazor-script) because the module is loaded and cached automatically. Adding a `<script>` tag prevents the module from loading.
 
 Use of scripts and modules for collocated JS in a Razor class library (RCL) is only supported for Blazor's JS interop mechanism based on the <xref:Microsoft.JSInterop.IJSRuntime> interface. If you're implementing [JavaScript `[JSImport]`/`[JSExport]` interop](xref:blazor/js-interop/import-export-interop), see <xref:blazor/js-interop/import-export-interop#razor-class-library-rcl-collocated-js-is-unsupported>.
 
diff --git a/aspnetcore/blazor/javascript-interoperability/call-javascript-from-dotnet.md b/aspnetcore/blazor/javascript-interoperability/call-javascript-from-dotnet.md
index 12a6e7fc5744..fa52010bf82d 100644
--- a/aspnetcore/blazor/javascript-interoperability/call-javascript-from-dotnet.md
+++ b/aspnetcore/blazor/javascript-interoperability/call-javascript-from-dotnet.md
@@ -623,7 +623,7 @@ In the preceding example:
   * The path segment for the current directory (`./`) is required in order to create the correct static asset path to the JS file.
   * The `{SCRIPT PATH AND FILE NAME (.js)}` placeholder is the path and file name under `wwwroot`.
 * Disposes the <xref:Microsoft.JSInterop.IJSObjectReference> for [garbage collection](xref:blazor/components/lifecycle#asynchronous-iasyncdisposable) in <xref:System.IAsyncDisposable.DisposeAsync%2A?displayProperty=nameWithType>.
-* Don't place a `<script>` tag for the script after the [Blazor script](xref:blazor/project-structure#location-of-the-blazor-script). The module is loaded automatically and cached. Adding a `<script>` tag results in the module not loading correctly.
+* Don't place a `<script>` tag for the script after the [Blazor script](xref:blazor/project-structure#location-of-the-blazor-script) because the module is loaded and cached automatically. Adding a `<script>` tag prevents the module from loading.
 
 Dynamically importing a module requires a network request, so it can only be achieved asynchronously by calling <xref:Microsoft.JSInterop.IJSRuntime.InvokeAsync%2A>.
 

From 4f930c7424e3b21281ca478cce818970afb1bdcf Mon Sep 17 00:00:00 2001
From: guardrex <1622880+guardrex@users.noreply.github.com>
Date: Fri, 3 Jan 2025 05:38:58 -0500
Subject: [PATCH 3/6] Updates

---
 aspnetcore/blazor/project-structure.md | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/aspnetcore/blazor/project-structure.md b/aspnetcore/blazor/project-structure.md
index da1602300b44..cc3a62298fe4 100644
--- a/aspnetcore/blazor/project-structure.md
+++ b/aspnetcore/blazor/project-structure.md
@@ -536,7 +536,10 @@ The project structure of the client-side app in a hosted Blazor Webassembly solu
 
 ## Location of the Blazor script
 
-The Blazor script is served from an embedded resource in the ASP.NET Core shared framework.
+The Blazor script, which is served from an embedded resource in the ASP.NET Core shared framework, handles:
+
+* Downloading the .NET runtime, Razor components, and the component's dependencies.
+* Initialization of the runtime.
 
 :::moniker range=">= aspnetcore-8.0"
 

From edc991f406a0b2f0daece5f349db7eb01fb6e374 Mon Sep 17 00:00:00 2001
From: guardrex <1622880+guardrex@users.noreply.github.com>
Date: Fri, 3 Jan 2025 05:40:18 -0500
Subject: [PATCH 4/6] Updates

---
 aspnetcore/blazor/hosting-models.md    | 2 +-
 aspnetcore/blazor/project-structure.md | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/aspnetcore/blazor/hosting-models.md b/aspnetcore/blazor/hosting-models.md
index e60b784d3bac..c4cb3357ddb3 100644
--- a/aspnetcore/blazor/hosting-models.md
+++ b/aspnetcore/blazor/hosting-models.md
@@ -97,7 +97,7 @@ A Blazor WebAssembly app built as a [Progressive Web App (PWA)](xref:blazor/prog
 
 The Blazor script handles:
 
-* Downloading the .NET runtime, Razor components, and the component's dependencies.
+* Downloading the .NET runtime, Razor components, and dependencies.
 * Initialization of the runtime.
 
 The size of the published app, its *payload size*, is a critical performance factor for an app's usability. A large app takes a relatively long time to download to a browser, which diminishes the user experience. Blazor WebAssembly optimizes payload size to reduce download times:
diff --git a/aspnetcore/blazor/project-structure.md b/aspnetcore/blazor/project-structure.md
index cc3a62298fe4..d5670acc9a30 100644
--- a/aspnetcore/blazor/project-structure.md
+++ b/aspnetcore/blazor/project-structure.md
@@ -538,7 +538,7 @@ The project structure of the client-side app in a hosted Blazor Webassembly solu
 
 The Blazor script, which is served from an embedded resource in the ASP.NET Core shared framework, handles:
 
-* Downloading the .NET runtime, Razor components, and the component's dependencies.
+* Downloading the .NET runtime, Razor components, and dependencies.
 * Initialization of the runtime.
 
 :::moniker range=">= aspnetcore-8.0"

From 3a2b2a5864418345ba86c1a5c136809ac80f4bd2 Mon Sep 17 00:00:00 2001
From: guardrex <1622880+guardrex@users.noreply.github.com>
Date: Fri, 3 Jan 2025 05:41:29 -0500
Subject: [PATCH 5/6] Updates

---
 aspnetcore/blazor/hosting-models.md    | 2 +-
 aspnetcore/blazor/project-structure.md | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/aspnetcore/blazor/hosting-models.md b/aspnetcore/blazor/hosting-models.md
index c4cb3357ddb3..62eaa29f7980 100644
--- a/aspnetcore/blazor/hosting-models.md
+++ b/aspnetcore/blazor/hosting-models.md
@@ -98,7 +98,7 @@ A Blazor WebAssembly app built as a [Progressive Web App (PWA)](xref:blazor/prog
 The Blazor script handles:
 
 * Downloading the .NET runtime, Razor components, and dependencies.
-* Initialization of the runtime.
+* Runtime initialization.
 
 The size of the published app, its *payload size*, is a critical performance factor for an app's usability. A large app takes a relatively long time to download to a browser, which diminishes the user experience. Blazor WebAssembly optimizes payload size to reduce download times:
 
diff --git a/aspnetcore/blazor/project-structure.md b/aspnetcore/blazor/project-structure.md
index d5670acc9a30..b86cfed336aa 100644
--- a/aspnetcore/blazor/project-structure.md
+++ b/aspnetcore/blazor/project-structure.md
@@ -539,7 +539,7 @@ The project structure of the client-side app in a hosted Blazor Webassembly solu
 The Blazor script, which is served from an embedded resource in the ASP.NET Core shared framework, handles:
 
 * Downloading the .NET runtime, Razor components, and dependencies.
-* Initialization of the runtime.
+* Runtime initialization.
 
 :::moniker range=">= aspnetcore-8.0"
 

From 9396d2090751461a81633176099a690417bb2aa8 Mon Sep 17 00:00:00 2001
From: guardrex <1622880+guardrex@users.noreply.github.com>
Date: Fri, 3 Jan 2025 05:52:50 -0500
Subject: [PATCH 6/6] Updates

---
 aspnetcore/blazor/includes/js-interop/js-collocation.md         | 2 +-
 .../javascript-interoperability/call-javascript-from-dotnet.md  | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/aspnetcore/blazor/includes/js-interop/js-collocation.md b/aspnetcore/blazor/includes/js-interop/js-collocation.md
index 48d52fc6d513..8804b10bf555 100644
--- a/aspnetcore/blazor/includes/js-interop/js-collocation.md
+++ b/aspnetcore/blazor/includes/js-interop/js-collocation.md
@@ -153,7 +153,7 @@ export function showPrompt2(message) {
 ```
 
 > [!IMPORTANT]
-> Don't place a `<script>` tag for `JsCollocation2.razor.js` after the [Blazor script](xref:blazor/project-structure#location-of-the-blazor-script) because the module is loaded and cached automatically. Adding a `<script>` tag prevents the module from loading.
+> Don't place a `<script>` tag for `JsCollocation2.razor.js` after the [Blazor script](xref:blazor/project-structure#location-of-the-blazor-script) because the module is loaded and cached automatically when the [dynamic `import()`](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Operators/import) is invoked.
 
 Use of scripts and modules for collocated JS in a Razor class library (RCL) is only supported for Blazor's JS interop mechanism based on the <xref:Microsoft.JSInterop.IJSRuntime> interface. If you're implementing [JavaScript `[JSImport]`/`[JSExport]` interop](xref:blazor/js-interop/import-export-interop), see <xref:blazor/js-interop/import-export-interop#razor-class-library-rcl-collocated-js-is-unsupported>.
 
diff --git a/aspnetcore/blazor/javascript-interoperability/call-javascript-from-dotnet.md b/aspnetcore/blazor/javascript-interoperability/call-javascript-from-dotnet.md
index fa52010bf82d..5068b93cd776 100644
--- a/aspnetcore/blazor/javascript-interoperability/call-javascript-from-dotnet.md
+++ b/aspnetcore/blazor/javascript-interoperability/call-javascript-from-dotnet.md
@@ -623,7 +623,7 @@ In the preceding example:
   * The path segment for the current directory (`./`) is required in order to create the correct static asset path to the JS file.
   * The `{SCRIPT PATH AND FILE NAME (.js)}` placeholder is the path and file name under `wwwroot`.
 * Disposes the <xref:Microsoft.JSInterop.IJSObjectReference> for [garbage collection](xref:blazor/components/lifecycle#asynchronous-iasyncdisposable) in <xref:System.IAsyncDisposable.DisposeAsync%2A?displayProperty=nameWithType>.
-* Don't place a `<script>` tag for the script after the [Blazor script](xref:blazor/project-structure#location-of-the-blazor-script) because the module is loaded and cached automatically. Adding a `<script>` tag prevents the module from loading.
+* Don't place a `<script>` tag for the script after the [Blazor script](xref:blazor/project-structure#location-of-the-blazor-script) because the module is loaded and cached automatically when the [dynamic `import()`](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Operators/import) is invoked.
 
 Dynamically importing a module requires a network request, so it can only be achieved asynchronously by calling <xref:Microsoft.JSInterop.IJSRuntime.InvokeAsync%2A>.