Usable wasm browser apps build output with WasmBundlerFriendlyBootConfig=true

[ArcadeMode]

It is currently not possible to use the output of a Wasm Browser App's dotnet build when WasmBundlerFriendlyBootConfig=true.

• Hotreload is still referenced from the generated boot.config.json. However there wont be a server involved to provide the files, nor are they present on disk.
• Static assets are not copied from wwwroot to the output directory

These two points make it so that builds will fail when passed into an npm project.

Secondary 'issues' (rather improvements)

• Compression is also enabled by default, slowing the build down while the js bundler most likely wont be using these files.
• Fingerprinting is also enabled by default, which the bundler can to (and often does) by itself.

Changes

• defaulted the aforementioned properties to false when building bundler friendly
• ammended static asset sdk 'default items' Content with instruction to also copy to the output directory on build.

Test are updated to always run an npm build when building bundler friendly, so multiple tests verify that this works. A new test was added to explicitly test for the absence of hot reload from the boot json.

Effect

The proposed changes make it no longer necessary to go through a dev cycle with publish + npm builds, instead the (faster) builds can be used for the npm builds. Once ready its ofcourse still possible to publish for a release build (a more typical development flow).

[Copilot]

Pull request overview

This PR aims to make WasmBundlerFriendlyBootConfig=true usable in Debug builds by preventing hot reload from being referenced in the generated boot config when no dev server/files are available (e.g., when bundling with a JS bundler).

Changes:

• Adds MSBuild logic to set WasmEnableHotReload=false when WasmBundlerFriendlyBootConfig=true (under certain conditions).

[Copilot]

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated 4 comments.

[ArcadeMode]

@pavelsavara could you look at this if you have a moment?

I added a build test to confirm the hotreload references are omitted when building bundler friendly, just in case.

[Copilot]

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.

[ArcadeMode]

Converted to draft, I was doing some things wrong. Will undraft when I got the tests working properly

[Copilot]

Pull request overview

Copilot reviewed 5 out of 5 changed files in this pull request and generated 2 comments.

[ArcadeMode]

@maraf This is ready for another review. I think there's been some good improvements.

[Copilot]

Pull request overview

Copilot reviewed 6 out of 6 changed files in this pull request and generated 2 comments.

[Copilot]

Pull request overview

Copilot reviewed 6 out of 6 changed files in this pull request and generated no new comments.

[ArcadeMode]

As discussed on Discord, the test coverage has been extended by including build+run tests. Had to resolve an issue with the build-time importmap. I did so by aligning it with the publish-time importmap. Its not particularly elegant, I hope we can propose a change to the sdk repo where this becomes a property so we can just flip the switch here.

[Copilot]

Pull request overview

Copilot reviewed 8 out of 8 changed files in this pull request and generated 1 comment.

[ArcadeMode]

this change resolves browser console errors due to the inability to load profiler.js. Its not actually used in any tests (yet), but now it could.