Split blazor.web.js into dynamically-loadable bundles

[SteveSandersonMS]

Ideally, people using SSR only (with progressive enhancement etc) would get a very small blazor.web.js that doesn't include any of the SignalR parts or any of the .NET WebAssembly runtime JS support library.

Then, if an interactive component was used, we'd use an ES module dependency to dynamically load the JS library needed for it. We could potentially split the "server" and "webassembly" bundles though they would have a lot in common. It might suffice just to split out the "interactive" parts from the "static" ones.

Thanks for contacting us.

We're moving this issue to the .NET 8 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

Thanks for contacting us.

We're moving this issue to the .NET 9 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.