[browser] Suport for OutputType Library #89577

Activity

1. pavelsavara

   added

   arch-wasmWebAssembly architectureWebAssembly architecture

   area-Infrastructure-mono

   on Jul 27, 2023
2. pavelsavara

   added this to the 9.0.0 milestone on Jul 27, 2023
4. maraf commented on Jun 4, 2024

   

   maraf

   on Jun 4, 2024

   Last edited by maraf

   Member

   More actions

   I'm slightly confused by the description. Is the goal here to produce a "wasm application without main" (the whole app bundle)? Or just be able to use [JSImport] in .NET library? For the latter, setting RuntimeIdentifier=browser-wasm should be sufficient. If the Microsoft.NET.Sdk.StaticWebAssets SDK is used, even the javascript files will be bundled correctly
5. pavelsavara commented on Jun 4, 2024

   

   pavelsavara

   on Jun 4, 2024

   MemberAuthor

   More actions

   For the "wasm application without main" what would be the use-case ?
   Could we have blazor component with wasm functionality as nuget and then add that to non-wasm blazor project and expect it to work ?

   Could we have dotnet wasm wrapped as react component and somehow flow it thru asp.net core in a way which would initialize the dotnet.js ?

   I feel that the answer is probably not with nuget.

   Could the same thing be achieved with npm package and node/webpack ecosystem ? Possibly yes.
6. maraf commented on Jun 4, 2024

   

   maraf

   on Jun 4, 2024

   Member

   More actions

   If it's not the "wasm application without main" case, we can close the issue
7. pavelsavara

   closed this as completedon Jun 4, 2024
8. github-actions

   locked and limited conversation to collaborators on Jul 5, 2024