-
Notifications
You must be signed in to change notification settings - Fork 12.3k
Publish blazor.*.js files to npm #10124
Copy link
Copy link
Open
Labels
Pillar: Technical DebtPriority:2Work that is important, but not critical for the releaseWork that is important, but not critical for the releaseaffected-fewThis issue impacts only small number of customersThis issue impacts only small number of customersarea-blazorIncludes: Blazor, Razor ComponentsIncludes: Blazor, Razor Componentsfeature-blazor-jsinteropThis issue is related to JSInterop in BlazorThis issue is related to JSInterop in Blazorseverity-minorThis label is used by an internal toolThis label is used by an internal tooltask
Milestone
Description
Activity
Metadata
Metadata
Assignees
Labels
Pillar: Technical DebtPriority:2Work that is important, but not critical for the releaseWork that is important, but not critical for the releaseaffected-fewThis issue impacts only small number of customersThis issue impacts only small number of customersarea-blazorIncludes: Blazor, Razor ComponentsIncludes: Blazor, Razor Componentsfeature-blazor-jsinteropThis issue is related to JSInterop in BlazorThis issue is related to JSInterop in Blazorseverity-minorThis label is used by an internal toolThis label is used by an internal tooltask
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.jsfile 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.jsinto my webpack build, by either accessing it through NPM or being able to link to it directly. However, according to dotnet/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.