[browser] Suport for OutputType Library

[pavelsavara]

currently WASM projects need to be <OutputType>Exe</OutputType>

use case: nuget library with component for Blazor, including [JSImport]

[ghost]

Tagging subscribers to this area: @directhex
See info in area-owners.md if you want to be subscribed.

Issue Details

---

currently WASM projects need to be <OutputType>Exe</OutputType>

Author:	pavelsavara
Assignees:	-
Labels:	arch-wasm, area-Infrastructure-mono
Milestone:	9.0.0

[maraf]

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

[pavelsavara]

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.

[maraf]

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