The dotnet watch tool currently has a hard-coded set of default WASM hot reload capabilities so that it can initialize before the WebAssembly runtime starts up.
We should consider having the runtime provide these capabilities, possibly by including them in a .props file so that they can get picked up by dotnet watch.
Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.
Issue Details
The `dotnet watch` tool currently has a [hard-coded](https://github.com/dotnet/sdk/blob/6f9c74184babc859b096f445edcc3c2f1a52d5bb/src/BuiltInTools/dotnet-watch/HotReload/BlazorWebAssemblyDeltaApplier.cs#L16-L18) set of default WASM hot reload capabilities so that it can initialize before the WebAssembly runtime starts up.
We should consider having the runtime provide these capabilities, possibly by including them in a `.props` file so that they can get picked up by `dotnet watch`.
Context: https://github.com/dotnet/aspnetcore/issues/51507.
The
dotnet watch
tool currently has a hard-coded set of default WASM hot reload capabilities so that it can initialize before the WebAssembly runtime starts up.We should consider having the runtime provide these capabilities, possibly by including them in a
.props
file so that they can get picked up bydotnet watch
.Context: https://github.com/dotnet/aspnetcore/issues/51507.