Publish blazor.*.js files to npm

I’m working on implementing some server-side Blazor components, but I have a lot of other Javascript functionality on the page. I would like to be able to include the needed blazor.server.js file in my webpack build process, instead of having to embed it directly on the page. This way all of the Javascript for my application gets included in one file.

I would like to be able to bundle blazor.server.js into my webpack build, by either accessing it through NPM or being able to link to it directly. However, according to aspnet/AspNetCore.Docs#12358 this is an embedded resource in the middleware, so I’m not sure how I can access it and include it in my build.

[SteveSandersonMS]

If it becomes possible to get the JS code from a different source, we should add some kind of exact version match checking at runtime, blocking the app from starting unless it’s exactly correct. Until now we’ve never had to deal with people using the wrong version of blazor.webassembly.js for their .NET runtime, and it would be good to avoid that becoming a possibility.

[TanayParikh]

Note as part of this task, we may want to consider adding official docs on how to use TypeScript with Blazor, environment/project configuration, etc.

cc/ @guardrex. No action now but just so it’s on your radar 😄