[browser] Add OutputType=Library tests

[ilonatommy]

Fixes #110620.

Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.

Comments suppressed due to low confidence (4)

src/mono/wasm/testassets/EntryPoints/LibraryMode.cs:3

• [nitpick] The class name 'Test' is too generic. Consider renaming it to something more descriptive, such as 'LibraryCallbackHandler'.

public unsafe class Test

src/mono/wasm/testassets/EntryPoints/LibraryMode.cs:6

• [nitpick] The method name 'MyCallback' is too generic. Consider renaming it to something more descriptive, such as 'HandleCallback'.

public static int MyCallback()

src/mono/wasi/Wasi.Build.Tests/WasiLibraryModeTests.cs:22

• The method LibraryModeBuildPublishRun is now parameterized with sdk and hasWasmAppBundle, but there are no test cases to cover the different behaviors based on these parameters. Consider adding test cases to ensure these scenarios are tested.

[Theory]

src/mono/wasi/testassets/LibraryMode.cs:3

• [nitpick] The class name 'Test' is too generic. Consider renaming it to something more descriptive like 'LibraryModeTest'.

public unsafe class Test

[pavelsavara]

please let's discuss the goals of this before we proceed further

[maraf]

please let's discuss the goals of this before we proceed further

The use-case on browser is something like this demo https://github.com/maraf/dotnet-wasm-react. It doesn't need main, because there is no single entrypoint from .NET point of view. The application is driven by JavaScript

[pavelsavara]

There are updated requirements in #110620 description

[maraf]

Please, add also an index.html and main.js to the library mode testasset. The main.js will start the runtime and instead of calling main, it will call just the JSExport. Ideally, also run the app in the browser