Update Blazor release notes

[guardrex]

Fixes #36628

Marek ... I might be incorrect, but it seems like the example that you were referring to is correct by design because it states the module is using the .js file extension ...

... a module named scripts.js in the app's wwwroot/js folder is fingerprinted by adding #[.{fingerprint}] before the file extension (.js):

... and then it goes on to say that if the dev wants to fingerprint .mjs files, they use StaticWebAssetFingerprintPattern.

We are adding StaticWebAssetFingerprintPattern with .mjs

Yes, but that's after the example of a .js module IF they want to use a different extension (or fingerprint expression). Perhaps, I can fix that lead-in line and make it more specific like this ...

To fingerprint additional JS modules with a different file extension or fingerprint expression in standalone Blazor WebAssembly apps, use the <StaticWebAssetFingerprintPattern> property in the app's project file (.csproj).

... which is on this PR.

However, I might be misunderstanding the feature/problem with what's in the article.

[maraf]

The twist is .js files are not fingerprinted by default, because we don't know if they will be loaded as modules as by other mechanism. We can fingeprint .js files only if they are modules and thus browser will apply importmap when resolving the URL.

[guardrex]

The behavior doesn't seem to match that. What am I missing in the following scenario? .........

If I create a plain (non-module) JS script (wwwroot/script.js) with a JS FN in it ...

function alertMessage() {
  alert("Hello from JavaScript!");
}

... and I add the fingerprint expression to its filename ...

<script src="script#[.{fingerprint}].js"></script>

It gets fingerprinted and placed into the import map ...

[maraf]

Does it work on publish output?

[guardrex]

Not sure ... I didn't test. I'll check that and see what happens. brb

[guardrex]

I see what you mean ... no ... it doesn't fingerprint that file after the app is published. I'm not sure if I was just being silly expecting it to work like that.

Anyway ... for the changes that we need here, let me try another pass on this to see if I can get the coverage right. I'm still a bit confused tho because .js files could be modules or not modules. Does the framework figure that out ... and then if the .js file is a module, it will do the fingerprinting?

Rubber 🦆 says 'no' to that. I just tried with type="module", and it doesn't fingerprint on publish.

[guardrex]

I'm attempting to understand this feature better, and I tried the MSBuild config for .mjs, but I get ...

The attribute "Include" in element <StaticWebAssetFingerprintPattern> is unrecognized. The project file is invalid on disk and was not reloaded.

Any idea what might be going wrong?

[guardrex]

Ah .... rubber 🦆 says, 'that's an <ItemGroup> you silly 🦖!' 🙈😆 ... We better add that to the coverage.

[guardrex]

@maraf ... Ok, I think 🤔 that I'm getting this feature now. See if the diff (I made two commits) covers what we need to say.

If so, I'll go into the reference article coverage next and make similar updates.