`WasmBootConfigFileName` doesn't work with WasmAppBuilder without additional configuration

[JakeYallop]

I recently upgraded a project to .NET 10 preview 4. As part of this, I set WasmBootConfigFileName to dotnet.boot.json, as I needed the json version of the boot config, rather than the now default dotnet.boot.js.

However, despite WasmBootConfigFileName correctly generating a dotnet.boot.json file on publish in the AppBundle directory, the bundled dotnet.js still attempts to load from dotnet.boot.js by default.

The easy way to work around this is to set configSrc to dotnet.boot.json, however I found this behaviour a bit surprising. Is this the intended pattern for using this msbuild property, or are there any plans to smooth out this behaviour?

[maraf]

The dotnet.js needs to know which file to fetch (if any). If the config name is different than the default one encoded in dotnet.js, it needs to be specified in JS. Also note that in later previews the boot config in embedded in dotnet.js by default.

Out of curiosity, why do you need json format?